lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 8 Oct 2020 10:04:27 -0600
From:   Jonathan Corbet <corbet@....net>
To:     John Hubbard <jhubbard@...dia.com>
Cc:     Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
        Jan Kara <jack@...e.cz>, David Sterba <dsterba@...e.com>,
        <linux-doc@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Documentation: filesystems: better locations for
 sysfs-pci, sysfs-tagging

On Wed, 7 Oct 2020 16:31:51 -0700
John Hubbard <jhubbard@...dia.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@...dia.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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ