mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Alex Tran <alex.t.tran@gmail.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Alex Tran <alex.t.tran@gmail.com>
Subject: Re: [PATCH v1 1/3] docs: filesystems: sysfs: remove top level sysfs net directory
Date: Thu, 18 Sep 2025 10:34:11 -0600	[thread overview]
Message-ID: <87a52r90u4.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250902023039.1351270-3-alex.t.tran@gmail.com>

Alex Tran <alex.t.tran@gmail.com> writes:

> The net/ directory is not present as a top level sysfs directory
> in standard Linux systems. Network interfaces can be accessible
> via /sys/class/net instead.
>
> Signed-off-by: Alex Tran <alex.t.tran@gmail.com>
> ---
>  Documentation/filesystems/sysfs.rst | 1 -
>  1 file changed, 1 deletion(-)
>
> diff --git a/Documentation/filesystems/sysfs.rst b/Documentation/filesystems/sysfs.rst
> index c32993bc83c7..c50da87f27fa 100644
> --- a/Documentation/filesystems/sysfs.rst
> +++ b/Documentation/filesystems/sysfs.rst
> @@ -299,7 +299,6 @@ The top level sysfs directory looks like::
>      hypervisor/
>      kernel/
>      module/
> -    net/
>      power/

I have applied these three, thanks.

jon

      reply	other threads:[~2025-09-18 16:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-02  2:30 [PATCH v1 3/3] docs: filesystems: sysfs: add remaining top level sysfs directory descriptions Alex Tran
2025-09-02  2:30 ` [PATCH v1 2/3] docs: filesystems: sysfs: clarify symlink destinations in dev and bus/devices descriptions Alex Tran
2025-09-02  2:30 ` [PATCH v1 1/3] docs: filesystems: sysfs: remove top level sysfs net directory Alex Tran
2025-09-18 16:34   ` Jonathan Corbet [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=87a52r90u4.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=alex.t.tran@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.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®