Linux-Next Archive on lore.kernel.org
 help / color / Atom feed
From: Rajat Jain <rajatja@google.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Greg KH <greg@kroah.com>,
	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: Tue, 1 Jun 2021 10:39:42 -0700
Message-ID: <CACK8Z6Fp-_oRkC-dQ4U5y6ZUrr7Q3U084PiP+Q9daYstpps+aA@mail.gmail.com> (raw)
In-Reply-To: <20210601183002.26176586@canb.auug.org.au>

Hello,


On Tue, Jun 1, 2021 at 1:30 AM 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/sysfs-devices-removable:2: WARNING: Unexpected indentation.
> Documentation/ABI/testing/sysfs-devices-removable:2: WARNING: Block quote ends without a blank line; unexpected unindent.

I'd be happy to send a patch to fix this, but I didn't really
understand what needs to be done.

Here is the relevant documentation update in the patch:

+What:          /sys/devices/.../removable
+Date:          May 2021
+Contact:       Rajat Jain <rajatxjain@gmail.com>
+Description:
+               Information about whether a given device can be removed from the
+               platform by the user. This is determined by its subsystem in a
+               bus / platform-specific way. This attribute is only present for
+               devices that can support determining such information:
+
+               "removable": device can be removed from the platform by the user
+               "fixed":     device is fixed to the platform / cannot be removed
+                            by the user.
+               "unknown":   The information is unavailable / cannot be deduced.
+
+               Currently this is only supported by USB (which infers the
+               information from a combination of hub descriptor bits and
+               platform-specific data such as ACPI).

I'd be happy to send a patch if you can point me what needs to be done
(or let Stephen / Greg / some one else do it if it is easier to just
do it instead of guiding me).

Thanks,

Rajat

>
> Introduced by commit
>
>   70f400d4d957 ("driver core: Move the "removable" attribute from USB to core")
>
> --
> Cheers,
> Stephen Rothwell

  reply index

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-01  8:30 Stephen Rothwell
2021-06-01 17:39 ` Rajat Jain [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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 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=CACK8Z6Fp-_oRkC-dQ4U5y6ZUrr7Q3U084PiP+Q9daYstpps+aA@mail.gmail.com \
    --to=rajatja@google.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

Linux-Next Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-next/0 linux-next/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-next linux-next/ https://lore.kernel.org/linux-next \
		linux-next@vger.kernel.org
	public-inbox-index linux-next

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-next


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git