From: Krzysztof Kozlowski <krzk@kernel.org>
To: Abdul Rahim <abdul.rahim@myyahoo.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] nfc: s3fwrn5: Prefer strscpy() over strcpy()
Date: Tue, 26 Nov 2024 10:22:37 +0100 [thread overview]
Message-ID: <5ad018d8-a2a2-4bf3-86d0-47bbe2c3d94d@kernel.org> (raw)
In-Reply-To: <myr4qk4h7pkvvsqzn4rpp2dqpuwkqwqllb6jgblkhwrzfy22r4@hozqqltux5om>
On 26/11/2024 09:49, Abdul Rahim wrote:
> On Tue, Nov 26, 2024 at 07:38:43AM +0100, Krzysztof Kozlowski wrote:
>> On 25/11/2024 21:41, Abdul Rahim wrote:
>>> Do i need to resend it. What additional information do I need to
>>> provide?
>>
>>
>> You cut entire email, no clue what's this.
>>
>> Best regards,
>> Krzysztof
>>
>
> Do I need to resend this patch [1]. You gave it `Reviewed-by` tag. But
> it's not applied yet.
>
> [1]: https://lore.kernel.org/lkml/20241029221641.15726-1-abdul.rahim@myyahoo.com/
First, it is merge window, no point to ping during that time. It is
actually highly discouraged, unless this is a fix. And it is not a fix.
Second, this should have net-next PATCH prefix, see subsystem profile
for networking.
I asked to change things in commit msg, so I expect next version, not
resend.
Best regards,
Krzysztof
prev parent reply other threads:[~2024-11-26 9:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241029221641.15726-1-abdul.rahim.ref@myyahoo.com>
2024-10-29 22:16 ` [PATCH] nfc: s3fwrn5: Prefer strscpy() over strcpy() Abdul Rahim
2024-10-30 5:57 ` Krzysztof Kozlowski
2024-11-25 20:41 ` Abdul Rahim
2024-11-26 6:38 ` Krzysztof Kozlowski
2024-11-26 8:49 ` Abdul Rahim
2024-11-26 9:22 ` Krzysztof Kozlowski [this message]
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=5ad018d8-a2a2-4bf3-86d0-47bbe2c3d94d@kernel.org \
--to=krzk@kernel.org \
--cc=abdul.rahim@myyahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.