From: Rahul Rameshbabu <rrameshbabu@nvidia.com>
To: Rahul Rameshbabu <rrameshbabu@nvidia.com>
Cc: Michal Kubecek <mkubecek@suse.cz>,
patchwork-bot+netdevbpf@kernel.org, netdev@vger.kernel.org,
vadim.fedorenko@linux.dev, jacob.e.keller@intel.com,
pabeni@redhat.com, kuba@kernel.org, davem@davemloft.net,
edumazet@google.com, gal@nvidia.com, tariqt@nvidia.com,
saeedm@nvidia.com, cjubran@nvidia.com, cratiu@nvidia.com,
wintera@linux.ibm.com
Subject: Re: [PATCH ethtool-next v2 0/2] Userspace code for ethtool HW TS statistics
Date: Wed, 24 Apr 2024 11:58:48 -0700 [thread overview]
Message-ID: <87plue8u3a.fsf@nvidia.com> (raw)
In-Reply-To: <87edb3w56g.fsf@nvidia.com>
On Wed, 17 Apr, 2024 23:32:45 -0700 Rahul Rameshbabu <rrameshbabu@nvidia.com> wrote:
> On Thu, 18 Apr, 2024 08:30:48 +0200 Michal Kubecek <mkubecek@suse.cz> wrote:
>> [[PGP Signed Part:Undecided]]
>> On Wed, Apr 17, 2024 at 09:30:30PM +0000, patchwork-bot+netdevbpf@kernel.org wrote:
>>> Hello:
>>>
>>> This series was applied to ethtool/ethtool.git (next)
>>> by Michal Kubecek <mkubecek@suse.cz>:
>>>
>>> On Wed, 17 Apr 2024 13:38:27 -0700 you wrote:
>>> > Adds support for querying statistics related to tsinfo if the kernel supports
>>> > such statistics.
>>> >
>>> > Changes:
>>> > v1->v2:
>>> > - Updated UAPI header copy to be based on a valid commit in the
>>> > net-next tree. Thanks Alexandra Winter <wintera@linux.ibm.com> for
>>> > the catch.
>>> > - Refactored logic based on a suggestion from Jakub Kicinski
>>> > <kuba@kernel.org>.
>>> >
>>> > [...]
>>>
>>> Here is the summary with links:
>>> - [ethtool-next,v2,1/2] update UAPI header copies
>>> https://git.kernel.org/pub/scm/network/ethtool/ethtool.git/commit/?id=d324940988f3
>>> - [ethtool-next,v2,2/2] netlink: tsinfo: add statistics support
>>> (no matching commit)
>>
>> Looks like the patchwork bot got a bit confused here. I accidentally
>> updated the UAPI header copies to the same mainline commit yesterday
>> which was probably identified as accepting the first patch. But the
>> second (i.e. the important one) is still in the queue.
>
> I saw this but was not sure it was intentional. Good to know it was
> pw-bot hiccup.
Following up since I noticed these commits have not landed in next
recently.
https://git.kernel.org/pub/scm/network/ethtool/ethtool.git/log/?h=next
--
Thanks,
Rahul Rameshbabu
prev parent reply other threads:[~2024-04-24 19:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 20:38 [PATCH ethtool-next v2 0/2] Userspace code for ethtool HW TS statistics Rahul Rameshbabu
2024-04-17 20:38 ` [PATCH ethtool-next v2 1/2] update UAPI header copies Rahul Rameshbabu
2024-04-17 20:38 ` [PATCH ethtool-next v2 2/2] netlink: tsinfo: add statistics support Rahul Rameshbabu
2024-04-17 21:30 ` [PATCH ethtool-next v2 0/2] Userspace code for ethtool HW TS statistics patchwork-bot+netdevbpf
2024-04-18 6:30 ` Michal Kubecek
2024-04-18 6:32 ` Rahul Rameshbabu
2024-04-24 18:58 ` Rahul Rameshbabu [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=87plue8u3a.fsf@nvidia.com \
--to=rrameshbabu@nvidia.com \
--cc=cjubran@nvidia.com \
--cc=cratiu@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=jacob.e.keller@intel.com \
--cc=kuba@kernel.org \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=patchwork-bot+netdevbpf@kernel.org \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
--cc=vadim.fedorenko@linux.dev \
--cc=wintera@linux.ibm.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).