From: Jakub Kicinski <kuba@kernel.org>
To: Martin Habets <habetsm.xilinx@gmail.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
davem@davemloft.net, pabeni@redhat.com, edumazet@google.com,
netdev@vger.kernel.org, ecree.xilinx@gmail.com,
linux-pci@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH net-next v2 0/2] sfc: Add EF100 BAR config support
Date: Thu, 14 Jul 2022 09:05:00 -0700 [thread overview]
Message-ID: <20220714090500.356846ea@kernel.org> (raw)
In-Reply-To: <Ys/+vCNAfh/AKuJv@gmail.com>
On Thu, 14 Jul 2022 12:32:12 +0100 Martin Habets wrote:
> > Okay. Indeed, we could easily bolt something onto devlink, I'd think
> > but I don't know the space enough to push for one solution over
> > another.
> >
> > Please try to document the problem and the solution... somewhere, tho.
> > Otherwise the chances that the next vendor with this problem follows
> > the same approach fall from low to none.
>
> Yeah, good point. The obvious thing would be to create a
> Documentation/networking/device_drivers/ethernet/sfc/sfc/rst
> Is that generic enough for other vendors to find out, or there a better place?
Documentation/vdpa.rst ? I don't see any kernel level notes on
implementing vDPA perhaps virt folks can suggest something.
I don't think people would be looking into driver-specific docs
when trying to implement an interface, so sfc is not a great option
IMHO.
> I can do a follow-up patch for this.
Let's make it part of the same series.
next prev parent reply other threads:[~2022-07-14 16:05 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 [this message]
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
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=20220714090500.356846ea@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=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.