All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Robert Hancock <robert.hancock@calian.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"michal.simek@xilinx.com" <michal.simek@xilinx.com>,
	"radhey.shyam.pandey@xilinx.com" <radhey.shyam.pandey@xilinx.com>,
	"edumazet@google.com" <edumazet@google.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH net-next v7 0/2] axienet NAPI improvements
Date: Thu, 12 May 2022 17:04:31 -0700	[thread overview]
Message-ID: <20220512170431.6b51fdd3@kernel.org> (raw)
In-Reply-To: <6f1c104d118c55b6903a0557ddba223d3e2843b1.camel@calian.com>

On Thu, 12 May 2022 23:00:02 +0000 Robert Hancock wrote:
> Looking at Patchwork and Lore, seems like this cover letter may not have made
> it to the list, though the two patches did? Can resend if it doesn't eventually
> show up..

I may be wrong but I think it's fine, the cover letter doesn't have
much extra info, lore will catch you quoting it here and thread that
with the patches.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Robert Hancock <robert.hancock@calian.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"michal.simek@xilinx.com" <michal.simek@xilinx.com>,
	"radhey.shyam.pandey@xilinx.com" <radhey.shyam.pandey@xilinx.com>,
	"edumazet@google.com" <edumazet@google.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH net-next v7 0/2] axienet NAPI improvements
Date: Thu, 12 May 2022 17:04:31 -0700	[thread overview]
Message-ID: <20220512170431.6b51fdd3@kernel.org> (raw)
In-Reply-To: <6f1c104d118c55b6903a0557ddba223d3e2843b1.camel@calian.com>

On Thu, 12 May 2022 23:00:02 +0000 Robert Hancock wrote:
> Looking at Patchwork and Lore, seems like this cover letter may not have made
> it to the list, though the two patches did? Can resend if it doesn't eventually
> show up..

I may be wrong but I think it's fine, the cover letter doesn't have
much extra info, lore will catch you quoting it here and thread that
with the patches.

  reply	other threads:[~2022-05-13  0:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220512171853.4100193-1-robert.hancock@calian.com>
2022-05-12 17:18 ` [PATCH net-next v7 1/2] net: axienet: Be more careful about updating tx_bd_tail Robert Hancock
2022-05-12 17:18   ` Robert Hancock
2022-05-13 11:30   ` patchwork-bot+netdevbpf
2022-05-13 11:30     ` patchwork-bot+netdevbpf
2022-05-12 17:18 ` [PATCH net-next v7 2/2] net: axienet: Use NAPI for TX completion path Robert Hancock
2022-05-12 17:18   ` Robert Hancock
2022-05-12 23:00 ` [PATCH net-next v7 0/2] axienet NAPI improvements Robert Hancock
2022-05-12 23:00   ` Robert Hancock
2022-05-13  0:04   ` Jakub Kicinski [this message]
2022-05-13  0:04     ` Jakub Kicinski

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=20220512170431.6b51fdd3@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=michal.simek@xilinx.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=radhey.shyam.pandey@xilinx.com \
    --cc=robert.hancock@calian.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 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.