Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: [GIT PULL] ata changes for 5.17-rc1
Date: Tue, 18 Jan 2022 09:06:44 +0900	[thread overview]
Message-ID: <9ae727e1-e4b1-c4ea-dbb5-5d0fff2f3c5d@opensource.wdc.com> (raw)
In-Reply-To: <CAHk-=wggW9TzY90pB-1Rfpqm0erxbKO++BR7AOMh_E7_o7cdwA@mail.gmail.com>

On 1/14/22 22:54, Linus Torvalds wrote:
> On Fri, Jan 14, 2022 at 7:59 AM Damien Le Moal
> <damien.lemoal@opensource.wdc.com> wrote:
>>
>> ATA changes for 5.17-rc1
> 
> A number of these commits are not in linux-next. Why?
> 
> It looks like you have rebased things very recently (and looks like
> you did it a week ago too). Or maybe some patch-queue system, or
> whatever. Why? If it hasn't been in linux-next, you should explain
> what's up.
> 
> As it is, I'm traveling, and I'm just throwing this away because I
> don't want things that haven't seen the build testing that linux-next
> does, since on my laptop I cannot do as much build testing as I
> normally do.
> 
>                     Linus

Hi Linus,

Any more concerns about this pull request ? Is there anything I need to
do to get it merged ?

All patches are in linux-next and I did not get any build-bot complaints.

Thanks.

-- 
Damien Le Moal
Western Digital Research

  parent reply	other threads:[~2022-01-18  0:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-14  6:59 [GIT PULL] ata changes for 5.17-rc1 Damien Le Moal
2022-01-14 13:54 ` Linus Torvalds
2022-01-14 23:27   ` Damien Le Moal
2022-01-14 23:37     ` Stephen Rothwell
2022-01-15  1:39       ` Damien Le Moal
2022-01-18  0:06   ` Damien Le Moal [this message]
2022-01-18  8:29 ` pr-tracker-bot

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=9ae727e1-e4b1-c4ea-dbb5-5d0fff2f3c5d@opensource.wdc.com \
    --to=damien.lemoal@opensource.wdc.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=torvalds@linux-foundation.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