linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Ingo.Rohloff@lauterbach.com" <Ingo.Rohloff@lauterbach.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH v3 1/1] usb: gadget: f_fs: Support zerocopy transfers via mmap.
Date: Sat, 12 Feb 2022 08:17:02 +0100	[thread overview]
Message-ID: <Ygde7hP9EtrA8tny@kroah.com> (raw)
In-Reply-To: <1043-6206bd00-1-213dc380@137639204>

On Fri, Feb 11, 2022 at 08:47:01PM +0100, Ingo.Rohloff@lauterbach.com wrote:
> Hello Greg,
> 
> On Friday, 11 February, 2022 12:02 CET, Greg KH <gregkh@linuxfoundation.org> wrote:
> 
> > On Wed, Feb 09, 2022 at 06:25:07PM +0100, Ingo Rohloff wrote:
> > > This patch implements the same functionality for FunctionFS as
> > > commit f7d34b445abc00e979b7 ("USB: Add support for usbfs zerocopy.")
> > > did for USB host devio.c
> > > ...
> >
> > No documentation of the new mount option here?
> > It should go somewhere, right?
> 
> You are of course right :-).
> But: Do you have any suggestions where to put it?

Where are other filesystem mount options listed?

> I just searched the "Documentation/" directory, but so far I haven't found
> any  description about the mount options available for FunctionFS
> (including the not so obvious "no_disconnect" option).

What about in Documentation/usb/functionfs.rst?

> Of course I can put some minimal description of the mount option
> in the commit message itself; but I think that's not really useful?

It is better than nothing :)

> So maybe it makes more sense to in general write more about FunctionFS.
> The whole mmap mechanism also might need a description somewhere.
> I have some test code here:
>   https://github.com/trace32/test_usb_ffs
> I can also provide that as a patch (with sign-off) , for example under 
>   tools/usb/ffs-aio-example
> (there already is some test code there).

Yes, test code would be great, can you add it to the self-test
framework?

> Would this make sense to you?  I guess that would make more sense as an
> extra patch; at least as an extra commit?

Yes, a patch series would be good.

thanks,

greg k-h

      parent reply	other threads:[~2022-02-12  7:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-09 17:25 [PATCH v3 0/1] Zerocopy for USB Gadget FunctionFS Ingo Rohloff
2022-02-09 17:25 ` [PATCH v3 1/1] usb: gadget: f_fs: Support zerocopy transfers via mmap Ingo Rohloff
2022-02-11 11:02   ` Greg KH
     [not found]     ` <1043-6206bd00-1-213dc380@137639204>
2022-02-12  7:17       ` Greg KH [this message]

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=Ygde7hP9EtrA8tny@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Ingo.Rohloff@lauterbach.com \
    --cc=linux-usb@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).