From: Phillip Potter <phil@philpotter.co.uk>
To: Christoph Hellwig <hch@lst.de>
Cc: Jonathan Corbet <corbet@lwn.net>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
linux-kernel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH 3/3] block: remove last remaining traces of IDE documentation
Date: Tue, 10 May 2022 09:09:17 +0100 [thread overview]
Message-ID: <Ynodrbf0LAh7GL1H@equinox> (raw)
In-Reply-To: <20220510055116.GB10576@lst.de>
On Tue, May 10, 2022 at 07:51:16AM +0200, Christoph Hellwig wrote:
> On Mon, May 09, 2022 at 04:17:31PM -0600, Jonathan Corbet wrote:
> > > This is not your fault, you couldn't have been expected to know this in
> > > retrospect, and I should probably look into getting my own tree/GPG key
> > > sorted to alleviate this problem in future.
> > >
> > > In the meantime, if you're comfortable with the idea, I can just resolve
> > > the conflict myself when I send the patches onto Jens this time and
> > > include patch 3/3 pre-fixed up. Merge window will be fairly soon anyway.
> >
> > So I'm a little confused by the state of everything at this point, but
> > I'm assuming that I need not worry about taking these changes through
> > docs-next. Please let me know if that's not correct.
>
> Same here, I'm a bit lost on what still needs to be done.
Hi Christoph,
Nothing needs doing, I will handle. Many thanks.
Regards,
Phil
prev parent reply other threads:[~2022-05-10 8:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 13:24 [PATCH 0/3] remove remaining IDE driver fragments Paul Gortmaker
2022-04-27 13:24 ` [PATCH 1/3] cdrom: remove the unused driver specific disc change ioctl Paul Gortmaker
2022-04-28 23:28 ` Phillip Potter
2022-04-27 13:24 ` [PATCH 2/3] cdrom: mark CDROMGETSPINDOWN/CDROMSETSPINDOWN obsolete Paul Gortmaker
2022-04-28 23:32 ` Phillip Potter
2022-04-27 13:24 ` [PATCH 3/3] block: remove last remaining traces of IDE documentation Paul Gortmaker
2022-04-27 14:50 ` Jonathan Corbet
2022-04-27 16:50 ` Randy Dunlap
2022-04-27 16:59 ` Paul Gortmaker
2022-04-28 23:43 ` Phillip Potter
2022-05-06 15:32 ` Paul Gortmaker
2022-05-06 17:54 ` Phillip Potter
2022-05-06 20:24 ` Paul Gortmaker
2022-05-06 20:27 ` Randy Dunlap
2022-05-07 20:57 ` Phillip Potter
2022-05-09 22:17 ` Jonathan Corbet
2022-05-09 23:03 ` Phillip Potter
2022-05-09 23:17 ` Jens Axboe
2022-05-10 8:00 ` Phillip Potter
2022-05-10 5:51 ` Christoph Hellwig
2022-05-10 8:09 ` Phillip Potter [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=Ynodrbf0LAh7GL1H@equinox \
--to=phil@philpotter.co.uk \
--cc=axboe@kernel.dk \
--cc=corbet@lwn.net \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=rdunlap@infradead.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