netdev - Re: [PATCH net-next] selftests: net: fix grammar in reuseaddr_ports

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAH4c4j+9aXmFTym_uU-RtQtNhPBMeWnEE-mZaAceQTmuL3QCTg@mail.gmail.com>
Date: Sat, 15 Feb 2025 23:53:33 +0530
From: Pranav Tyagi <pranav.tyagi03@...il.com>
To: Simon Horman <horms@...nel.org>
Cc: netdev@...r.kernel.org, linux-kernel-mentees@...ts.linux.dev, 
	skhan@...uxfoundation.org
Subject: Re: [PATCH net-next] selftests: net: fix grammar in
 reuseaddr_ports_exhausted.c log message

Hi Simon,

Thank you for reviewing my patch and for the guidance on the submission process.

I sincerely apologize for the duplicate posting—I’ll make sure to
follow the correct versioning and reposting guidelines moving forward.
I’m still new to the community and getting familiar with the workflow,
so I really appreciate your feedback. I’ll keep these best practices
in mind for future submissions.

Regards,
Pranav Tyagi

On Sat, Feb 15, 2025 at 7:15 PM Simon Horman <horms@...nel.org> wrote:
>
> On Thu, Feb 13, 2025 at 08:56:11PM +0530, Pranav Tyagi wrote:
> > This patch fixes a grammatical error in a test log message in
> > reuseaddr_ports_exhausted.c for better clarity as a part of lfx
> > application tasks
> >
> > Signed-off-by: Pranav Tyagi <pranav.tyagi03@...il.com>
>
> Thanks Pranav,
>
> This change looks good to me.
>
> Reviewed-by: Simon Horman <horms@...nel.org>
>
>
> A note on process to keep in mind for next time:
>
> This patch seems to have been posted to netdev twice, about 20 hours apart.
> Please don't do that as it can be quite confusing to reviewers.
>
> If you need to update a patch, please version it (e.g. [PATCH v2 net-next).
> If you need to repost a patch, say because there has been no response for a
> long time, please label it accordingly (e.g. [PATCH REPOST net-next]) and
> include some explanation of why it is being reposted, e.g. below the
> scissors ("---").
>
> And regardless, when posting a patch to netdev, please don't post it more
> than once every 24h.