From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: linuxtestproject.agent@gmail.com
Cc: ltp@lists.linux.it
Subject: Re: [LTP] lib: safe_file_ops: Add SAFE_FILE_READ_STR()
Date: Thu, 07 May 2026 08:29:29 +0000 [thread overview]
Message-ID: <69fc4d6a.050a0220.3c2011.edbc@mx.google.com> (raw)
In-Reply-To: <20260507082645.3925-1-linuxtestproject.agent@gmail.com>
Hi,
> Hi Cyril,
>
> --- [PATCH 1/2] ---
>
> On Thu, 7 May 2026, Cyril Hrubis wrote:
> > lib: safe_file_ops: Add SAFE_FILE_READ_STR()
>
> > + if (!fgets(buf, buf_size, f))
> > + buf[0] = 0;
> > +
> > + size_t len = strlen(buf);
>
> Move `size_t len` to the top of the function alongside `FILE *f`; mixed
> declarations after executable statements violate kernel coding style.
I see this is happening again. I'm gonna add a rule for it.
>
> --- [PATCH 2/2] ---
>
> On Thu, 7 May 2026, Cyril Hrubis wrote:
> > syscalls: newuname01: Fix fail on empty domainname
>
> > Fixes: https://github.com/linux-test-project/ltp/issues/1304
>
> `Fixes:` must reference a git commit hash in the form
> `Fixes: <hash> ("<subject>")`. Use `Closes:` to reference GitHub issues.
>
This is actually correct. I will change the Fixes to Closes
before merge.
Regards,
--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-05-07 8:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 7:50 [LTP] [PATCH v2 0/2] Fix proc parsing in newuname01 Cyril Hrubis
2026-05-07 7:50 ` [LTP] [PATCH v2 1/2] lib: safe_file_ops: Add SAFE_FILE_READ_STR() Cyril Hrubis
2026-05-07 8:26 ` [LTP] " linuxtestproject.agent
2026-05-07 8:29 ` Andrea Cervesato via ltp [this message]
2026-05-07 8:29 ` [LTP] [PATCH v2 1/2] " Andrea Cervesato via ltp
2026-05-07 7:50 ` [LTP] [PATCH v2 2/2] syscalls: newuname01: Fix fail on empty domainname Cyril Hrubis
2026-05-07 8:29 ` Andrea Cervesato via ltp
2026-05-07 8:34 ` [LTP] [PATCH v2 0/2] Fix proc parsing in newuname01 Andrea Cervesato via ltp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=69fc4d6a.050a0220.3c2011.edbc@mx.google.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=linuxtestproject.agent@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox