From: Jakub Kicinski <kuba@kernel.org>
To: Martin Habets <habetsm.xilinx@gmail.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>, davem <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
netdev <netdev@vger.kernel.org>,
ecree.xilinx@gmail.com, linux-pci@vger.kernel.org,
virtualization <virtualization@lists.linux-foundation.org>,
mst <mst@redhat.com>
Subject: Re: [PATCH net-next v2 0/2] sfc: Add EF100 BAR config support
Date: Fri, 12 Aug 2022 12:18:56 -0700 [thread overview]
Message-ID: <20220812121856.2e212b4d@kernel.org> (raw)
In-Reply-To: <YvYfmw44gpuqexYz@gmail.com>
On Fri, 12 Aug 2022 10:38:35 +0100 Martin Habets wrote:
> FYI, during my holiday my colleagues found a way to use the vdpa tool for this.
> That means we should not need this series, at least for vDPA.
> So we can drop this series.
🎉 small victories :)
next prev parent reply other threads:[~2022-08-12 19:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 13:07 [PATCH net-next v2 0/2] sfc: Add EF100 BAR config support Martin Habets
2022-07-07 13:07 ` [PATCH net-next v2 1/2] " Martin Habets
2022-07-07 13:07 ` [PATCH net-next v2 2/2] sfc: Implement change of BAR configuration Martin Habets
2022-07-07 15:55 ` [PATCH net-next v2 0/2] sfc: Add EF100 BAR config support Bjorn Helgaas
2022-07-07 15:55 ` Bjorn Helgaas
2022-07-11 13:38 ` Martin Habets
2022-07-11 18:48 ` Jakub Kicinski
2022-07-13 8:40 ` Martin Habets
2022-07-13 18:48 ` Jakub Kicinski
2022-07-14 11:32 ` Martin Habets
2022-07-14 16:05 ` Jakub Kicinski
2022-08-03 7:57 ` Jason Wang
2022-08-03 7:57 ` Jason Wang
2022-08-12 9:38 ` Martin Habets
2022-08-12 19:18 ` Jakub Kicinski [this message]
2022-07-11 22:00 ` Bjorn Helgaas
2022-07-11 22:00 ` Bjorn Helgaas
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=20220812121856.2e212b4d@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=habetsm.xilinx@gmail.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=virtualization@lists.linux-foundation.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 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.