public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	Anders Larsen <al@alarsen.net>,
	linux-doc@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, kernel-janitors@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: Re: [PATCH 0/2] Minor documentation clean-up in fs
Date: Tue, 14 Mar 2023 12:53:20 -0600	[thread overview]
Message-ID: <87sfe7qi5b.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230220170210.15677-1-lukas.bulwahn@gmail.com>

Lukas Bulwahn <lukas.bulwahn@gmail.com> writes:

> Dear Jonathan,
>
> please pick this minor documentation clean-up in fs. It is not in the
> Documentation directory, but I would consider these README files also
> some unsorted largely distributed kernel documentation.
>
> Here is some trivial and probably little-to-debate clean up.
>  
> Lukas Bulwahn (2):
>   qnx6: credit contributor and mark filesystem orphan
>   qnx4: credit contributors in CREDITS
>
>  CREDITS        | 16 ++++++++++++++++
>  MAINTAINERS    |  6 ++++++
>  fs/qnx4/README |  9 ---------
>  fs/qnx6/README |  8 --------
>  4 files changed, 22 insertions(+), 17 deletions(-)
>  delete mode 100644 fs/qnx4/README
>  delete mode 100644 fs/qnx6/README

Applied, thanks.

jon

      parent reply	other threads:[~2023-03-14 18:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-20 17:02 [PATCH 0/2] Minor documentation clean-up in fs Lukas Bulwahn
2023-02-20 17:02 ` [PATCH 1/2] qnx6: credit contributor and mark filesystem orphan Lukas Bulwahn
2023-02-20 17:02 ` [PATCH 2/2] qnx4: credit contributors in CREDITS Lukas Bulwahn
2023-02-20 17:07   ` Anders Larsen
2023-03-14 18:53 ` 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=87sfe7qi5b.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=al@alarsen.net \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    /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