From: Alan Stern <stern@rowland.harvard.edu>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Nikita Yushchenko <nikita.yoush@cogentembedded.com>,
Felipe Balbi <balbi@kernel.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Petr Nechaev <petr.nechaev@cogentembedded.com>
Subject: Re: [PATCH v3] usb: gadget: storage: add support for media larger than 2T
Date: Tue, 5 Oct 2021 10:19:58 -0400 [thread overview]
Message-ID: <20211005141958.GA621017@rowland.harvard.edu> (raw)
In-Reply-To: <YVwyDsuIT9lZWi2v@kroah.com>
On Tue, Oct 05, 2021 at 01:07:58PM +0200, Greg Kroah-Hartman wrote:
> On Tue, Sep 21, 2021 at 05:59:02PM +0300, Nikita Yushchenko wrote:
> > This adds support for READ_CAPACITY(16), READ(16) and WRITE(16)
> > commands, and fixes READ_CAPACITY command to return 0xffffffff if
> > media size does not fit in 32 bits.
> >
> > This makes f_mass_storage to export a 16T disk array correctly.
> >
> > Signed-off-by: Nikita Yushchenko <nikita.yoush@cogentembedded.com>
> > ---
> > v3:
> > - added this changelog
> >
> > v2:
> > - fixed call to check_command() for READ_CAPACITY(16)
> > - fixed alphabetical order of commands in switch statement
> > - renamed variable, added comments, and fixed formatting, per advices by
> > Alan Stern <stern@rowland.harvard.edu>
>
> Felipe and Alan, any objections to this change?
No objections. In fact, I already sent my Acked-by for v2 of the
patch (which is the same as v3):
https://marc.info/?l=linux-usb&m=163165151506682&w=2
Alan Stern
next prev parent reply other threads:[~2021-10-05 14:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 5:27 [PATCH] " Nikita Yushchenko
2021-09-14 15:13 ` Alan Stern
2021-09-14 20:09 ` [PATCH v2] " Nikita Yushchenko
2021-09-14 20:32 ` Alan Stern
2021-09-21 14:29 ` Greg Kroah-Hartman
2021-09-21 14:59 ` [PATCH v3] " Nikita Yushchenko
2021-10-05 11:07 ` Greg Kroah-Hartman
2021-10-05 12:07 ` Felipe Balbi
2021-10-05 14:19 ` Alan Stern [this message]
2021-10-10 13:08 ` Greg Kroah-Hartman
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=20211005141958.GA621017@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nikita.yoush@cogentembedded.com \
--cc=petr.nechaev@cogentembedded.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
all inboxes | Powered by JetHome®