public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: John Hubbard <jhubbard@nvidia.com>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Jan Kara <jack@suse.cz>, David Sterba <dsterba@suse.com>,
	<linux-doc@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Documentation: filesystems: better locations for sysfs-pci, sysfs-tagging
Date: Thu, 8 Oct 2020 10:04:27 -0600	[thread overview]
Message-ID: <20201008100427.39ca3c1f@lwn.net> (raw)
In-Reply-To: <20201007233151.490953-1-jhubbard@nvidia.com>

On Wed, 7 Oct 2020 16:31:51 -0700
John Hubbard <jhubbard@nvidia.com> wrote:

> sysfs-pci and sysfs-tagging were mis-filed: their locations with
> Documentation/ implied that they were related to file systems. Actually,
> each topic is about a very specific *use* of sysfs, and sysfs *happens*
> to be a (virtual) filesystem, so this is not really the right place.
> 
> It's jarring to be reading about filesystems in general and then come
> across these specific details about PCI, and tagging...and then back to
> general filesystems again.
> 
> Move sysfs-pci and sysfs-tagging to a location under the sysfs topic.
> 
> Signed-off-by: John Hubbard <jhubbard@nvidia.com>

I see why you want to do this, but I have to wonder if moving them out of
Documentation/filesystems entirely might not be a better approach.
sysfs-pci.rst might better belong in the admin guide or under PCI/, while
sysfs-tagging.rst could go under networking/.

Make sense?

Thanks,

jon

  reply	other threads:[~2020-10-08 16:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-07 23:31 [PATCH] Documentation: filesystems: better locations for sysfs-pci, sysfs-tagging John Hubbard
2020-10-08 16:04 ` Jonathan Corbet [this message]
2020-10-08 19:28   ` John Hubbard

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=20201008100427.39ca3c1f@lwn.net \
    --to=corbet@lwn.net \
    --cc=dsterba@suse.com \
    --cc=jack@suse.cz \
    --cc=jhubbard@nvidia.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@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