From: Randy Dunlap <rdunlap@infradead.org>
To: Paul Gortmaker <paul.gortmaker@windriver.com>,
Phillip Potter <phil@philpotter.co.uk>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-kernel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 3/3] block: remove last remaining traces of IDE documentation
Date: Fri, 6 May 2022 13:27:11 -0700 [thread overview]
Message-ID: <056303ce-1837-4d1e-a9fb-3e20e3686d59@infradead.org> (raw)
In-Reply-To: <20220506202434.GJ12977@windriver.com>
On 5/6/22 13:24, Paul Gortmaker wrote:
> [Re: [PATCH 3/3] block: remove last remaining traces of IDE documentation] On 06/05/2022 (Fri 18:54) Phillip Potter wrote:
>
>> On Fri, May 06, 2022 at 11:32:41AM -0400, Paul Gortmaker wrote:
>
> [...]
>
>>> Are you working off linux-next? If not, what is your baseline and what
>>> are you running and what do you see? For example, the commands below:
>>>
>>> The ecb86 that I sent in this e-mail still applies on linux-next of
>>> today which contains Jens next as you can see:
>>>
>>
>> I was yes, the point I was trying to make (poorly) is that your patch
>> conflicts with Randy's patch which itself is not yet in linux-next, as
>> normally I send everything together at the start of the merge window to
>> Jens, as I don't have my own kernel.org tree yet, and usually I only get
>> one or two patches in a cycle anyway.
>>
>> 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.
>
> Sure, go ahead - just fix up things so all the last bits are gone; don't
> even worry about patch attribution; I don't care about that.
Thank for the cleanups, Paul.
--
~Randy
next prev parent reply other threads:[~2022-05-06 20:27 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 [this message]
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
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=056303ce-1837-4d1e-a9fb-3e20e3686d59@infradead.org \
--to=rdunlap@infradead.org \
--cc=axboe@kernel.dk \
--cc=corbet@lwn.net \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=phil@philpotter.co.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.