From: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>,
Max Staudt <max@enpas.org>, Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
linux-can@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH net] can: can327: fix snprintf() limit in can327_handle_prompt()
Date: Fri, 15 Nov 2024 00:24:17 +0900 [thread overview]
Message-ID: <7d4b176b-6b44-450b-ab2d-847e5199d1b9@wanadoo.fr> (raw)
In-Reply-To: <0c4ebaf0-a6c5-4852-939b-e7ac135f6f32@stanley.mountain>
On 15/11/2024 at 00:08, Dan Carpenter wrote:
> I'm happy to re-write the commit message. Changing snprintf to sprintf() makes
> me so much less happy...
OK. Let me amend my previous message. I kind of understood from the past
exchanges that Max will take the ownership of this patch and credit you
a with a Reported-by: tag.
If you keep the ownership of the patch, then that's a different story :)
I do not want to make you sad and I am fine with your preferred approach.
Yours sincerely,
Vincent Mailhol
next prev parent reply other threads:[~2024-11-14 15:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 9:03 [PATCH net] can: can327: fix snprintf() limit in can327_handle_prompt() Dan Carpenter
2024-11-14 9:19 ` Max Staudt
2024-11-14 9:26 ` Dan Carpenter
2024-11-14 9:29 ` Dan Carpenter
2024-11-14 10:11 ` Max Staudt
2024-11-14 9:34 ` Vincent Mailhol
2024-11-14 9:57 ` Dan Carpenter
2024-11-14 12:35 ` Vincent Mailhol
2024-11-14 13:34 ` Marc Kleine-Budde
2024-11-14 14:54 ` Vincent Mailhol
2024-11-14 15:08 ` Dan Carpenter
2024-11-14 15:24 ` Vincent Mailhol [this message]
2024-11-14 15:42 ` Dan Carpenter
2024-11-19 0:48 ` Max Staudt
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=7d4b176b-6b44-450b-ab2d-847e5199d1b9@wanadoo.fr \
--to=mailhol.vincent@wanadoo.fr \
--cc=andrew+netdev@lunn.ch \
--cc=dan.carpenter@linaro.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=max@enpas.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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