netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, pabeni@redhat.com, edumazet@google.com,
	netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/3][pull request] Intel Wired LAN Driver Updates 2023-10-02 (i40e, iavf)
Date: Wed, 4 Oct 2023 17:24:18 -0700	[thread overview]
Message-ID: <20231004172418.30f9c6b0@kernel.org> (raw)
In-Reply-To: <20231004172228.211ad344@kernel.org>

On Wed, 4 Oct 2023 17:22:28 -0700 Jakub Kicinski wrote:
> On Mon,  2 Oct 2023 11:50:31 -0700 Tony Nguyen wrote:
> > The following are changes since commit 436e5f758d6fbc2c5903d59f2cf9bb753ec77d9e:
> >   Merge branch 'mlxsw-next'
> > and are available in the git repository at:
> >   git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue 40GbE
> > 
> > Christophe JAILLET (1):
> >   iavf: Avoid a memory allocation in iavf_print_link_message()  
> 
> I don't see this one on the branch, I'll apply from the list..

Actually, I see that there was some discussion on the patch recently.
I'll let you sort this out and repost, maybe it's intentional :)

      reply	other threads:[~2023-10-05  0:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-02 18:50 [PATCH net-next 0/3][pull request] Intel Wired LAN Driver Updates 2023-10-02 (i40e, iavf) Tony Nguyen
2023-10-02 18:50 ` [PATCH net-next 1/3] i40e: Add rx_missed_errors for buffer exhaustion Tony Nguyen
2023-10-02 18:50 ` [PATCH net-next 2/3] iavf: remove "inline" functions from iavf_txrx.c Tony Nguyen
2023-10-02 18:50 ` [PATCH net-next 3/3] iavf: Avoid a memory allocation in iavf_print_link_message() Tony Nguyen
2023-10-05  0:22 ` [PATCH net-next 0/3][pull request] Intel Wired LAN Driver Updates 2023-10-02 (i40e, iavf) Jakub Kicinski
2023-10-05  0:24   ` Jakub Kicinski [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=20231004172418.30f9c6b0@kernel.org \
    --to=kuba@kernel.org \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --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;
as well as URLs for NNTP newsgroup(s).