netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: parav@nvidia.com, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2] uapi: add vdpa.h
Date: Mon, 18 Jul 2022 16:40:12 +0000	[thread overview]
Message-ID: <165816241279.22901.10228940243657683172.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220718163112.11023-1-stephen@networkplumber.org>

Hello:

This patch was applied to iproute2/iproute2.git (main)
by Stephen Hemminger <stephen@networkplumber.org>:

On Mon, 18 Jul 2022 09:31:13 -0700 you wrote:
> Iproute2 depends on kernel headers and all necessary kernel headers
> should be in iproute tree. When vdpa was added the kernel header
> file was not.
> 
> Fixes: c2ecc82b9d4c ("vdpa: Add vdpa tool")
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> 
> [...]

Here is the summary with links:
  - [iproute2] uapi: add vdpa.h
    https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=291898c5ff88

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  reply	other threads:[~2022-07-18 16:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18 16:31 [PATCH iproute2] uapi: add vdpa.h Stephen Hemminger
2022-07-18 16:40 ` patchwork-bot+netdevbpf [this message]
2022-07-18 16:42   ` Parav Pandit
2022-07-18 16:40 ` Parav Pandit
2022-07-18 16:50   ` Stephen Hemminger
2022-07-18 16:55   ` Stephen Hemminger
2022-07-18 17:51     ` David Ahern
2022-07-18 20:18       ` Stephen Hemminger

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=165816241279.22901.10228940243657683172.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=parav@nvidia.com \
    --cc=stephen@networkplumber.org \
    /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).