Append a newline character to the sysfs_emit() output in ptp_ocp_tty_show.
This aligns with common kernel conventions and improves readability for
userspace tools that expect newline-terminated values.

Signed-off-by: Zhongqiu Han <zhongqiu.han@oss.qualcomm.com>
---
 drivers/ptp/ptp_ocp.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/ptp/ptp_ocp.c b/drivers/ptp/ptp_ocp.c
index a5c363252986..cdff357456aa 100644
--- a/drivers/ptp/ptp_ocp.c
+++ b/drivers/ptp/ptp_ocp.c
@@ -3430,7 +3430,7 @@ ptp_ocp_tty_show(struct device *dev, struct device_attribute *attr, char *buf)
 	struct dev_ext_attribute *ea = to_ext_attr(attr);
 	struct ptp_ocp *bp = dev_get_drvdata(dev);
 
-	return sysfs_emit(buf, "ttyS%d", bp->port[(uintptr_t)ea->var].line);
+	return sysfs_emit(buf, "ttyS%d\n", bp->port[(uintptr_t)ea->var].line);
 }
 
 static umode_t
-- 
2.43.0

On Thu, 30 Oct 2025 20:45:19 +0800 Zhongqiu Han wrote:
> Append a newline character to the sysfs_emit() output in ptp_ocp_tty_show.
> This aligns with common kernel conventions and improves readability for
> userspace tools that expect newline-terminated values.

Vadim? Is the backward compat here a concern?

On 31/10/2025 23:59, Jakub Kicinski wrote:
> On Thu, 30 Oct 2025 20:45:19 +0800 Zhongqiu Han wrote:
>> Append a newline character to the sysfs_emit() output in ptp_ocp_tty_show.
>> This aligns with common kernel conventions and improves readability for
>> userspace tools that expect newline-terminated values.
> 
> Vadim? Is the backward compat here a concern?

Well, unfortunately, this patch breaks software we use:

openat(AT_FDCWD, "/dev/ttyS4\n", O_RDWR|O_NONBLOCK) = -1 ENOENT (No such 
file or directory)
newfstatat(AT_FDCWD, "/etc/localtime", {st_mode=S_IFREG|0644, 
st_size=114, ...}, 0) = 0
write(2, "23:40:33 \33[31mERROR\33[0m ", 2423:40:33 ERROR ) = 24
write(2, "Could not open sa5x device\n", 27Could not open sa5x device

So it looks like uAPI change, which is already used...

On Sat, 1 Nov 2025 23:45:00 +0000 Vadim Fedorenko wrote:
> On 31/10/2025 23:59, Jakub Kicinski wrote:
> > On Thu, 30 Oct 2025 20:45:19 +0800 Zhongqiu Han wrote:  
> >> Append a newline character to the sysfs_emit() output in ptp_ocp_tty_show.
> >> This aligns with common kernel conventions and improves readability for
> >> userspace tools that expect newline-terminated values.  
> > 
> > Vadim? Is the backward compat here a concern?  
> 
> Well, unfortunately, this patch breaks software we use:
> 
> openat(AT_FDCWD, "/dev/ttyS4\n", O_RDWR|O_NONBLOCK) = -1 ENOENT (No such 
> file or directory)
> newfstatat(AT_FDCWD, "/etc/localtime", {st_mode=S_IFREG|0644, 
> st_size=114, ...}, 0) = 0
> write(2, "23:40:33 \33[31mERROR\33[0m ", 2423:40:33 ERROR ) = 24
> write(2, "Could not open sa5x device\n", 27Could not open sa5x device
> 
> So it looks like uAPI change, which is already used...
> 

Zhongqiu Han please consider sending a patch to add a comment above 
the unfortunate emit() explaining that we can't change it now.
I get the feeling that otherwise this "fix" may resurface.
-- 
pw-bot: cr

On 11/3/2025 8:00 AM, Jakub Kicinski wrote:
> On Sat, 1 Nov 2025 23:45:00 +0000 Vadim Fedorenko wrote:
>> On 31/10/2025 23:59, Jakub Kicinski wrote:
>>> On Thu, 30 Oct 2025 20:45:19 +0800 Zhongqiu Han wrote:
>>>> Append a newline character to the sysfs_emit() output in ptp_ocp_tty_show.
>>>> This aligns with common kernel conventions and improves readability for
>>>> userspace tools that expect newline-terminated values.
>>>
>>> Vadim? Is the backward compat here a concern?
>>
>> Well, unfortunately, this patch breaks software we use:
>>
>> openat(AT_FDCWD, "/dev/ttyS4\n", O_RDWR|O_NONBLOCK) = -1 ENOENT (No such
>> file or directory)
>> newfstatat(AT_FDCWD, "/etc/localtime", {st_mode=S_IFREG|0644,
>> st_size=114, ...}, 0) = 0
>> write(2, "23:40:33 \33[31mERROR\33[0m ", 2423:40:33 ERROR ) = 24
>> write(2, "Could not open sa5x device\n", 27Could not open sa5x device
>>
>> So it looks like uAPI change, which is already used...
>>
> 
> Zhongqiu Han please consider sending a patch to add a comment above
> the unfortunate emit() explaining that we can't change it now.
> I get the feeling that otherwise this "fix" may resurface.

Hi Jakub,
Sure, will send the comment patch. Thanks


-- 
Thx and BRs,
Zhongqiu Han

On 31/10/2025 23:59, Jakub Kicinski wrote:
> On Thu, 30 Oct 2025 20:45:19 +0800 Zhongqiu Han wrote:
>> Append a newline character to the sysfs_emit() output in ptp_ocp_tty_show.
>> This aligns with common kernel conventions and improves readability for
>> userspace tools that expect newline-terminated values.
> 
> Vadim? Is the backward compat here a concern?

I'm checking our software now, hopefully it will not break, but I need a
bit of time to be sure