mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: taozj888  <taozj888@163.com>
To: "Jacob Keller" <jacob.e.keller@intel.com>
Cc: theo.lebrun@bootlin.com,
	"Conor Dooley" <conor.dooley@microchip.com>,
	"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>,
	"Haavard Skinnemoen" <hskinnemoen@atmel.com>,
	"Jeff Garzik" <jeff@garzik.org>,
	"open list:NETWORKING DRIVERS" <netdev@vger.kernel.org>,
	"open list" <linux-kernel@vger.kernel.org>
Subject: Re:Re: [PATCH net v3 0/1] brief description about the patch and its
Date: Wed, 7 Oct 2026 13:55:13 +0800 (CST)	[thread overview]
Message-ID: <66801d4d.16ab.1a114ee2256.Coremail.taozj888@163.com> (raw)
In-Reply-To: <d69249a8-210f-405d-9cd5-715245fecb8c@intel.com>















Hi Jacob:

Thanks.
Zijin Tao

At 2026-10-07 05:23:33, "Jacob Keller" <jacob.e.keller@intel.com> wrote:
>On 10/4/2026 6:39 AM, taozj888@163.com wrote:
>> From: taozijin <taozj888@163.com>
>> 
>> 
>> This patch is titled as:
>>   net: macb: rate limit netdev error info print in the data path
>> 
>> Changes since v1:
>> 
>> v3: 
>> - add this change log since v2 missing it
>> - drop the blank line between the assignment sentence and the commit
>>   info
>> 
>> v2:
>> 
>> - update the commit message with the reason why the unlimit prints would
>>   bother/delay booting process
>> - update the commit message with the Fix commit id provided which is
>>   suggested by Théo Lebrun<theo.lebrun@bootlin.com>
>> - update the commit message with what packet type would trigger the
>>   error printings more easily.
>> 
>> v1:
>> 
>> - initial commit
>> 
>
>For single patches, it is typical to send this as part of the same

>message below your commit message with '---'.


OK, I will add the changelog in the commit message below '---' in the next patch.>
>To make that easier to handle, if you use git format-patch and git
>send-email you can use --annotate with git send-email to insert the
>contents before sending the email. If you use b4, it will automatically
>generate the correct format from its cover letter and the individual patch.
>
>If you do send a standalone cover letter, the subject would be better as
>just repeating the subject for the individual patch.
>
>I don't recall if netdev has any enforced or encoded policy here, so
>this is just a comment to hopefully help ease future contributions.
>
>Thanks,
>Jake
>
>> Best Regards,
>> 
>> Zijin Tao
>>  drivers/net/ethernet/cadence/macb_main.c | 14 ++++++++------
>>  1 file changed, 8 insertions(+), 6 deletions(-)
>> 

      reply	other threads:[~2026-10-07  5:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-04 13:39 taozj888
2026-10-04 13:39 ` [PATCH net v3 1/1] net: macb: rate limit netdev error info print in the data path taozj888
2026-10-06 21:25   ` Jacob Keller
2026-10-06 21:23 ` [PATCH net v3 0/1] brief description about the patch and its Jacob Keller
2026-10-07  5:55   ` taozj888 [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=66801d4d.16ab.1a114ee2256.Coremail.taozj888@163.com \
    --to=taozj888@163.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=conor.dooley@microchip.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hskinnemoen@atmel.com \
    --cc=jacob.e.keller@intel.com \
    --cc=jeff@garzik.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=theo.lebrun@bootlin.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

all inboxes | Powered by JetHome®