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>, <richardcochran@gmail.com>,
<jacob.e.keller@intel.com>
Subject: Re: [PATCH net-next 0/7][pull request] 1GbE Intel Wired LAN Driver Updates 2022-07-28
Date: Mon, 1 Aug 2022 10:22:16 -0700 [thread overview]
Message-ID: <20220801102216.340ffae8@kernel.org> (raw)
In-Reply-To: <46909de8-3555-5bc6-2e2b-e139941f640f@intel.com>
On Mon, 1 Aug 2022 09:56:27 -0700 Tony Nguyen wrote:
> I'm seeing this as "Accepted" on Patchworks [1], but I haven't seen a
> patchwork bot notification or am I seeing it on the tree. I think it may
> have accidentally been marked so just wanted to get it back on the radar.
Ack, back to the queue it goes, sorry about that.
next prev parent reply other threads:[~2022-08-01 17:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 18:18 [PATCH net-next 0/7][pull request] 1GbE Intel Wired LAN Driver Updates 2022-07-28 Tony Nguyen
2022-07-28 18:18 ` [PATCH net-next 1/7] ice: implement adjfine with mul_u64_u64_div_u64 Tony Nguyen
2022-07-28 18:18 ` [PATCH net-next 2/7] e1000e: remove unnecessary range check in e1000e_phc_adjfreq Tony Nguyen
2022-07-28 18:18 ` [PATCH net-next 3/7] e1000e: convert .adjfreq to .adjfine Tony Nguyen
2022-07-28 18:18 ` [PATCH net-next 4/7] i40e: use mul_u64_u64_div_u64 for PTP frequency calculation Tony Nguyen
2022-07-28 18:18 ` [PATCH net-next 5/7] i40e: convert .adjfreq to .adjfine Tony Nguyen
2022-07-28 18:18 ` [PATCH net-next 6/7] ixgbe: " Tony Nguyen
2022-07-28 18:18 ` [PATCH net-next 7/7] igb: " Tony Nguyen
2022-08-01 16:56 ` [PATCH net-next 0/7][pull request] 1GbE Intel Wired LAN Driver Updates 2022-07-28 Tony Nguyen
2022-08-01 17:22 ` Jakub Kicinski [this message]
2022-08-01 18:30 ` patchwork-bot+netdevbpf
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=20220801102216.340ffae8@kernel.org \
--to=kuba@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jacob.e.keller@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.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.