linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Costa Shulyupin <costa.shul@redhat.com>,
	linux-doc@vger.kernel.org, Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Costa Shulyupin <costa.shul@redhat.com>,
	open list <linux-kernel@vger.kernel.org>,
	"open list:BPF [MISC]" <bpf@vger.kernel.org>
Subject: Re: [PATCH v3] Documentation: subsystem-apis: Categorize remaining subsystems
Date: Fri, 09 Jun 2023 02:05:59 -0600	[thread overview]
Message-ID: <87h6rhoyag.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230601145556.3927838-1-costa.shul@redhat.com>

Costa Shulyupin <costa.shul@redhat.com> writes:

> From: Bagas Sanjaya <bagasdotme@gmail.com>
>
> Add classes:
> * Core subsystems
> * Storage
> * Networking
> * Peripherals and devices
> * Embedded systems
> * Integrity
> * Virtualization
> * Miscellaneous
>
> There is a FIXME that says to organize subsystems listed in
> subsystem-apis.rst. Fulfill it by categorize remaining subsytems
> by purpose/themes, while sorting entries in each category.
>
> HID devices are already categorized in 3c591cc954d56e ("docs:
> consolidate human interface subsystems").
>
> Signed-off-by: Costa Shulyupin <costa.shul@redhat.com>

So now that I've found a moment to look at stuff, I'm a bit confused
here.  Up top, you have a From: line identifying Bagas as the author of
this patch - but it lacks his signoff so I can't apply it.

If this is *really* such a complex change that it needs a
co-developed-by tag, please arrange that and the correct signoffs.
Otherwise, please send a patch that's your work (which can certainly
reflect suggestions from others) that is properly tagged.

Thanks,

jon

  parent reply	other threads:[~2023-06-09  8:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-29  8:55 [PATCH] docs: consolidate storage interfaces Costa Shulyupin
2023-05-30  8:54 ` Bagas Sanjaya
2023-05-31 10:17   ` [PATCH] docs: organize subsystems Costa Shulyupin
2023-06-01  3:13     ` Bagas Sanjaya
2023-06-01 14:55       ` [PATCH v3] Documentation: subsystem-apis: Categorize remaining subsystems Costa Shulyupin
2023-06-01 16:28         ` Randy Dunlap
2023-06-02 10:08         ` Bagas Sanjaya
2023-06-02 10:19           ` Jonathan Corbet
2023-06-02 12:33             ` Bagas Sanjaya
2023-06-09  8:05         ` Jonathan Corbet [this message]
2023-06-18  6:29           ` [PATCH v4] docs: consolidate storage interfaces Costa Shulyupin
2023-06-18 15:19             ` Randy Dunlap
2023-06-18 16:09               ` Costa Shulyupin
2023-06-21 15:33             ` Jonathan Corbet

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=87h6rhoyag.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=bagasdotme@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=costa.shul@redhat.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;
as well as URLs for NNTP newsgroup(s).