From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jens Axboe <axboe@kernel.dk>, David Miller <davem@davemloft.net>,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
"Alexander A. Klimov" <grandmaster@al2klimov.de>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Christoph Hellwig <hch@lst.de>,
Finn Thain <fthain@linux-m68k.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Vaibhav Gupta <vaibhavgupta40@gmail.com>
Subject: Re: linux-next: manual merge of the block tree with the ide and kspp-gustavo trees
Date: Mon, 21 Jun 2021 13:56:13 +0300 [thread overview]
Message-ID: <CAHp75VcJKX4xzP1PrCBixDzgGBGwVvbV3YtMebKxpRoi1_EhaA@mail.gmail.com> (raw)
In-Reply-To: <20210621141110.548ec3d0@canb.auug.org.au>
On Mon, Jun 21, 2021 at 7:13 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 2c8cbe0b2971 ("IDE SUBSYSTEM: Replace HTTP links with HTTPS ones")
> 9a51ffe845e4 ("ide: use generic power management")
> f9e09a0711ca ("ide: sc1200: use generic power management")
> d41b375134a9 ("ide: delkin_cb: use generic power management")
> 6800cd8cbc6e ("ide-acpi: use %*ph to print small buffer")
> 731d5f441e1c ("ide: Fix fall-through warnings for Clang")
>
> from the ide and kspp-gustavo trees and commits:
As far as I can tell the IDE hasn't sent PR to LInus for a long time
(like a few release cycles). I don't know what happened there, though.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-06-21 10:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 4:11 linux-next: manual merge of the block tree with the ide and kspp-gustavo trees Stephen Rothwell
2021-06-21 10:56 ` Andy Shevchenko [this message]
2021-06-21 12:30 ` Stephen Rothwell
2021-06-28 11:36 ` Andy Shevchenko
2021-06-28 22:50 ` Stephen Rothwell
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=CAHp75VcJKX4xzP1PrCBixDzgGBGwVvbV3YtMebKxpRoi1_EhaA@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=fthain@linux-m68k.org \
--cc=grandmaster@al2klimov.de \
--cc=gustavo@embeddedor.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=vaibhavgupta40@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;
as well as URLs for NNTP newsgroup(s).