From: Greg KH <gregkh@linuxfoundation.org>
To: chengdong zhou <zhouscd@gmail.com>
Cc: dan.scally@ideasonboard.com, laurent.pinchart@ideasonboard.com,
m.grzeschik@pengutronix.de, john@keeping.me.uk,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB: gadget: Fix the function name error in sourcesink/loopback.
Date: Tue, 1 Aug 2023 09:34:59 +0200 [thread overview]
Message-ID: <2023080152-bakeshop-shanty-2033@gregkh> (raw)
In-Reply-To: <CAN4mUXNZomVDfve1p_2D6G38MXd=gWLdg3=eSUMnFcWhcyb2EA@mail.gmail.com>
On Tue, Aug 01, 2023 at 03:27:04PM +0800, chengdong zhou wrote:
> Thank you for your patient response.
>
> On Tue, Aug 1, 2023 at 2:23 PM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> >
> > Please document this in the changelog text.
>
> But I can't find the changelog text anywhere.
That is what you are writing here for the commit. Please read the
kernel documentation for how to submit a patch, it will explain this.
> > But you changed the name:
> >
> > > > > - ss->function.name = "source/sink";
> > > > > + ss->function.name = "sourcesink";
> >
> > isn't that visable to userspace?
>
> Yes, I removed the "/". Because the macro definition
> DECLARE_USB_FUNCTION_INIT does not support "/".
> Should I stick with the original "SourceSink"? I think using the
> Linux-style "sourcesink" is better. By the way, due to the current
> bug, no one should be able to use "source/sink" in userspace.
But doesn't the '/' mean that you have a subdirectory here? What did
userspace look like before this, and what does it look like now?
thanks,
greg k-h
next prev parent reply other threads:[~2023-08-01 7:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 4:54 [PATCH] USB: gadget: Fix the function name error in sourcesink/loopback zhouscd
2023-08-01 5:06 ` Greg KH
2023-08-01 6:15 ` 周城东
2023-08-01 6:22 ` Greg KH
2023-08-01 7:27 ` chengdong zhou
2023-08-01 7:34 ` Greg KH [this message]
2023-08-01 8:00 ` chengdong zhou
2023-08-01 14:57 ` kernel test robot
2023-08-01 21:39 ` kernel test robot
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=2023080152-bakeshop-shanty-2033@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dan.scally@ideasonboard.com \
--cc=john@keeping.me.uk \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.grzeschik@pengutronix.de \
--cc=zhouscd@gmail.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