From: Greg KH <gregkh@linuxfoundation.org>
To: 周城东 <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 08:22:49 +0200 [thread overview]
Message-ID: <2023080108-resilient-citation-9a34@gregkh> (raw)
In-Reply-To: <CAN4mUXNNM-25oCx1jjVqqoPpX1P8Z4zkjh84Azprz52O4_AMNw@mail.gmail.com>
On Tue, Aug 01, 2023 at 02:15:50PM +0800, 周城东 wrote:
> Hi, Greg KH
>
> > I do not understand this text at all, sorry.
> > What exactly is broken and what is changed here to resolve the issue?
>
> The reason for the problem is that the value of struct
> usb_function.name is "loopback", while struct usb_function_driver.name
> is "Loopback". The same issue exists for sourcesink. When using USB
> Config FS, it won't be possible to enable these two functions.
Please document this in the changelog text.
> > And please use your full name for patches.
>
> I'm sorry, this is my first time sending kernel patch. How should I
> modify my name for the patch that has already been sent? Or should I
> resend a new patch?
Yes, you need to send a new version, please read the section entitled
"The canonical patch format" in the kernel file,
Documentation/process/submitting-patches.rst for what needs to be done
here.
> > You just changed a user-visable api, right? Where did you document this
> > and what will it affect?
>
> Yes, I removed lb_modexit and lb_modinit and used a simpler method for
> function initialization. This does not affect any other
> functionalities. In the old way, the loopback function was called by
> sslb_modinit in sourcesink. I believe this is not a good approach as
> the loopback and sourcesink should be independent functionalities.
> Their purpose is to provide simple examples for USB beginners like myself.
But you changed the name:
> > > - ss->function.name = "source/sink";
> > > + ss->function.name = "sourcesink";
isn't that visable to userspace?
thanks,
greg k-h
next prev parent reply other threads:[~2023-08-01 6:24 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 [this message]
2023-08-01 7:27 ` chengdong zhou
2023-08-01 7:34 ` Greg KH
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=2023080108-resilient-citation-9a34@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