From: Dominique Martinet <asmadeus@codewreck.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Michael Grzeschik <m.grzeschik@pengutronix.de>,
Eric Van Hensbergen <ericvh@kernel.org>,
Latchesar Ionkov <lucho@ionkov.net>,
Christian Schoenebeck <linux_oss@crudebyte.com>,
Jonathan Corbet <corbet@lwn.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
v9fs@lists.linux.dev, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
kernel@pengutronix.de
Subject: Re: [PATCH 1/3] usb: gadget: function: 9pfs
Date: Tue, 16 Jan 2024 13:04:08 +0900 [thread overview]
Message-ID: <ZaYAONB-fUB3gjBl@codewreck.org> (raw)
In-Reply-To: <4856923e-3ce8-4372-9451-f9c8aa157111@rowland.harvard.edu>
Alan Stern wrote on Mon, Jan 15, 2024 at 10:17:34PM -0500:
> > diff --git a/drivers/usb/gadget/Kconfig b/drivers/usb/gadget/Kconfig
> > index b3592bcb0f966..72cdecaef6aa9 100644
> > --- a/drivers/usb/gadget/Kconfig
> > +++ b/drivers/usb/gadget/Kconfig
> > @@ -153,6 +153,10 @@ config USB_F_ACM
> > config USB_F_SS_LB
> > tristate
> >
> > +config USB_F_9PFS
> > + tristate
> > + select NET_9P
> > +
> > config USB_U_SERIAL
> > tristate
> >
> > @@ -363,6 +367,13 @@ config USB_CONFIGFS_F_LB_SS
> > test software, like the "usbtest" driver, to put your hardware
> > and its driver through a basic set of functional tests.
> >
> > +config USB_CONFIGFS_F_9PFS
> > + bool "9pfs over usb gadget"
> > + depends on USB_CONFIGFS
> > + select USB_F_9PFS
> > + help
> > + 9pfs support for usb gadget
>
> This may be a dumb question, but what is the purpose of this CONFIG
> symbol? It doesn't get used by any of the patches in this series, as
> far as I can see.
USB_F_9PFS cannot be selected directly in menuconfig so this allows
configuring the build option -- that appears to be how the other usb
gadgets are configured so I assume it's done that way for consistency
more than out of necessity (I don't see a problem in making the build
system use USB_CONFIGFS_F_9PFS directly, it'd just be different from the
rest)
--
Dominique Martinet | Asmadeus
next prev parent reply other threads:[~2024-01-16 4:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 1:49 [PATCH 0/3] usb: gadget: 9pfs transport Michael Grzeschik
2024-01-16 1:49 ` [PATCH 1/3] usb: gadget: function: 9pfs Michael Grzeschik
2024-01-16 3:17 ` Alan Stern
2024-01-16 4:04 ` Dominique Martinet [this message]
2024-01-16 15:45 ` Alan Stern
2024-01-16 11:34 ` kernel test robot
2024-01-16 12:04 ` kernel test robot
2024-01-16 19:51 ` kernel test robot
2024-01-16 21:14 ` Christophe JAILLET
2024-01-17 0:02 ` kernel test robot
2024-01-16 1:49 ` [PATCH 2/3] usb: gadget: legacy: add 9pfs multi gadget Michael Grzeschik
2024-01-16 18:05 ` kernel test robot
2024-01-16 1:49 ` [PATCH 3/3] tools: usb: p9_fwd: add usb gadget packet forwarder script Michael Grzeschik
2024-01-16 11:45 ` [PATCH 0/3] usb: gadget: 9pfs transport Dominique Martinet
2024-01-16 15:51 ` Jan Lübbe
2024-01-17 10:54 ` Dominique Martinet
2024-01-26 19:47 ` Andrzej Pietrasiewicz
2024-01-26 21:57 ` Michael Grzeschik
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=ZaYAONB-fUB3gjBl@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=corbet@lwn.net \
--cc=ericvh@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@pengutronix.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=m.grzeschik@pengutronix.de \
--cc=stern@rowland.harvard.edu \
--cc=v9fs@lists.linux.dev \
/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.