mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Hubbard <jhubbard@nvidia.com>
To: Jonathan Corbet <corbet@lwn.net>
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 12:28:21 -0700	[thread overview]
Message-ID: <d91a1088-641c-07e1-4065-bbd8ad79332c@nvidia.com> (raw)
In-Reply-To: <20201008100427.39ca3c1f@lwn.net>

On 10/8/20 9:04 AM, Jonathan Corbet wrote:
> 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?
> 

Absolutely, I'll post a v2 that does it that way.

thanks,
-- 
John Hubbard
NVIDIA

      reply	other threads:[~2020-10-08 19:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-07 23:31 John Hubbard
2020-10-08 16:04 ` Jonathan Corbet
2020-10-08 19:28   ` John Hubbard [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=d91a1088-641c-07e1-4065-bbd8ad79332c@nvidia.com \
    --to=jhubbard@nvidia.com \
    --cc=corbet@lwn.net \
    --cc=dsterba@suse.com \
    --cc=jack@suse.cz \
    --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

all inboxes | Powered by JetHome®