From: Eric Biggers <ebiggers@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Bart Van Assche <bvanassche@acm.org>,
linux-block@vger.kernel.org, linux-doc@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/8] docs: consolidate sysfs-block into Documentation/ABI/
Date: Sun, 9 Jan 2022 13:25:51 -0800 [thread overview]
Message-ID: <YdtS3x0M1qFcN3R1@sol.localdomain> (raw)
In-Reply-To: <ef487b83-a1cc-d8a5-8a45-d0fec5eed94b@kernel.dk>
On Sun, Jan 09, 2022 at 10:01:11AM -0700, Jens Axboe wrote:
> On 1/7/22 1:58 PM, Bart Van Assche wrote:
> > On 1/6/22 13:41, Eric Biggers wrote:
> >> Jens, any reason you haven't applied this series yet? It looks like you've been
> >> applying other patches. To be clear, I've been expecting that this would go in
> >> through the block tree, rather than the docs tree.
> >
> > We are close to the v5.17 merge window so this is not a good time for a maintainer to
> > apply a large patch series. If Jens does not reply I propose to repost this patch
> > series after the v5.17 merge window has closed (three weeks from now?).
>
> I'm fine with it, but it should probably just go through the doc tree.
I think it makes much more sense for subsystems to be responsible for their own
documentation; that's why patch 8 in this series adds the block layer
documentation to the block layer MAINTAINERS entry. Do you disagree with that?
- Eric
next prev parent reply other threads:[~2022-01-09 21:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 0:38 [PATCH v3 0/8] docs: consolidate sysfs-block into Documentation/ABI/ Eric Biggers
2021-12-09 0:38 ` [PATCH v3 1/8] docs: sysfs-block: move to stable directory Eric Biggers
2021-12-09 0:38 ` [PATCH v3 2/8] docs: sysfs-block: sort alphabetically Eric Biggers
2021-12-09 0:38 ` [PATCH v3 3/8] docs: sysfs-block: add contact for nomerges Eric Biggers
2021-12-09 0:38 ` [PATCH v3 4/8] docs: sysfs-block: fill in missing documentation from queue-sysfs.rst Eric Biggers
2021-12-09 0:38 ` [PATCH v3 5/8] docs: sysfs-block: document stable_writes Eric Biggers
2021-12-09 0:38 ` [PATCH v3 6/8] docs: sysfs-block: document virt_boundary_mask Eric Biggers
2021-12-09 0:38 ` [PATCH v3 7/8] docs: block: remove queue-sysfs.rst Eric Biggers
2021-12-09 0:38 ` [PATCH v3 8/8] MAINTAINERS: add entries for block layer documentation Eric Biggers
2021-12-21 15:41 ` [PATCH v3 0/8] docs: consolidate sysfs-block into Documentation/ABI/ Eric Biggers
2022-01-03 15:06 ` Eric Biggers
2022-01-06 21:41 ` Eric Biggers
2022-01-07 20:58 ` Bart Van Assche
2022-01-09 17:01 ` Jens Axboe
2022-01-09 21:25 ` Eric Biggers [this message]
2022-01-10 1:58 ` Jens Axboe
2022-01-11 0:37 ` Jonathan Corbet
2022-01-10 1:59 ` Jens Axboe
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=YdtS3x0M1qFcN3R1@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-block@vger.kernel.org \
--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