All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxim Devaev <mdevaev@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the usb tree
Date: Sat, 23 Jul 2022 10:14:28 +0300	[thread overview]
Message-ID: <20220723101428.347d941e@reki> (raw)
In-Reply-To: <YtaUYmzTfKmx0Ek0@kroah.com>

On Tue, 19 Jul 2022 13:24:18 +0200
Greg KH <greg@kroah.com> wrote:

> On Tue, Jul 19, 2022 at 01:25:59PM +0300, Maxim Devaev wrote:
> > В Tue, 19 Jul 2022 19:43:37 +1000
> > Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >   
> > > Hi all,
> > > 
> > > After merging the usb tree, today's linux-next build (htmldocs) produced
> > > this warning:
> > > 
> > > Documentation/ABI/testing/configfs-usb-gadget-mass-storage:17: WARNING: Malformed table.
> > > Text in column margin in table line 14.
> > > 
> > > ===========     ==============================================
> > > file            The path to the backing file for the LUN.
> > >                 Required if LUN is not marked as removable.
> > > ro              Flag specifying access to the LUN shall be
> > >                 read-only. This is implied if CD-ROM emulation
> > >                 is enabled as well as when it was impossible
> > >                 to open "filename" in R/W mode.
> > > removable       Flag specifying that LUN shall be indicated as
> > >                 being removable.
> > > cdrom           Flag specifying that LUN shall be reported as
> > >                 being a CD-ROM.
> > > nofua           Flag specifying that FUA flag
> > >                 in SCSI WRITE(10,12)
> > > forced_eject    This write-only file is useful only when
> > >                 the function is active. It causes the backing
> > >                 file to be forcibly detached from the LUN,
> > >                 regardless of whether the host has allowed it.
> > >                 Any non-zero number of bytes written will
> > >                 result in ejection.
> > > ===========     ==============================================
> > > 
> > > Introduced by commit
> > > 
> > >   421c8d9a20da ("usb: gadget: f_mass_storage: forced_eject attribute")
> > >   
> > 
> > Sorry. Should I send a patch?  
> 
> Yes please.

JFYI the patch has been sent to linux-docs@, etc. I forgot to add you to CC.

  reply	other threads:[~2022-07-23  7:14 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-19  9:43 linux-next: build warning after merge of the usb tree Stephen Rothwell
2022-07-19 10:25 ` Maxim Devaev
2022-07-19 11:24   ` Greg KH
2022-07-23  7:14     ` Maxim Devaev [this message]
2022-07-23  7:26       ` Greg KH
2022-07-23  7:44         ` Maxim Devaev
  -- strict thread matches above, loose matches on Subject: below --
2024-01-08  5:02 Stephen Rothwell
2024-01-08  7:54 ` Greg KH
2024-01-25  0:35   ` Stephen Rothwell
2024-01-25  5:53     ` Krishna Kurapati PSSNV
2024-01-25 15:53       ` Greg KH
2023-02-06  3:50 Stephen Rothwell
2023-02-06  7:29 ` Greg KH
2023-02-06  7:45 ` Dan Scally
2023-02-06  9:22   ` Greg KH
2023-02-06 12:30   ` Bagas Sanjaya
2023-01-23  4:24 Stephen Rothwell
2023-01-23 14:42 ` Greg KH
2023-01-25 17:01   ` Jó Ágila Bitsch
2022-01-06 15:48 Stephen Rothwell
2022-01-06 16:10 ` Greg KH
2022-01-07 10:02   ` Pavel Hofman
2022-01-07 10:35     ` Greg KH
2021-06-01  8:30 Stephen Rothwell
2021-06-01 17:39 ` Rajat Jain
2021-06-04 13:37   ` Greg KH
2021-07-13 21:03     ` Rajat Jain
2021-07-08  2:22 ` Stephen Rothwell
2021-07-08  8:10   ` Greg KH
2021-04-26 12:44 Stephen Rothwell
2021-04-26 12:53 ` Greg KH
2021-05-21  0:40   ` Stephen Rothwell
2021-05-21  1:28     ` Fabio Estevam
2021-04-26 12:37 Stephen Rothwell
2021-04-26 12:53 ` Greg KH
2021-04-26 21:12   ` Thinh Nguyen
2021-03-10  2:49 Stephen Rothwell
2021-04-21  6:07 ` Stephen Rothwell
2021-04-21  6:22   ` Greg KH
2021-03-03  6:05 Stephen Rothwell
2021-02-03  5:13 Stephen Rothwell
2021-02-03  7:04 ` Benson Leung
2021-01-06  2:12 Stephen Rothwell
2021-01-13 22:48 ` Stephen Rothwell
2021-01-14  8:51   ` Greg KH
2020-11-20  5:15 Stephen Rothwell
2020-11-20  6:38 ` Prashant Malani
2020-01-06  3:41 Stephen Rothwell
2020-01-06  7:58 ` Krzysztof Kozlowski
2020-01-06  9:30   ` Greg KH
2018-09-11  2:47 Stephen Rothwell
2018-09-11  8:12 ` Greg KH
2017-11-02  4:06 Stephen Rothwell
2013-12-10  3:59 Stephen Rothwell
2012-11-02  4:08 Stephen Rothwell
2012-11-02  9:07 ` Felipe Balbi
2012-11-02  9:07   ` Felipe Balbi
2012-11-02 14:18   ` Alan Stern
2012-11-02 14:18     ` Alan Stern
2010-11-17  2:14 Stephen Rothwell
2010-11-17  4:20 ` Greg KH
2010-05-17  6:16 Stephen Rothwell
2010-05-17 18:01 ` Greg KH
2010-05-17  6:09 Stephen Rothwell
2010-05-17 18:01 ` Greg KH

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=20220723101428.347d941e@reki \
    --to=mdevaev@gmail.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.