From: Tejun Heo <tj@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Samuel Morris <samorris@lexmark.com>,
Tony Lindgren <tony@atomide.com>, Roger Quadros <rogerq@ti.com>,
Naresh Kamboju <naresh.kamboju@linaro.org>,
linux-omap@vger.kernel.org,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
ssantosh@kernel.org, Olof Johansson <olof@lixom.net>,
Tero Kristo <t-kristo@ti.com>,
"Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: 4.18.0-rc1-next-20180619 boot failed on beagle board x15
Date: Mon, 6 Aug 2018 10:24:24 -0700 [thread overview]
Message-ID: <20180806172424.GC410235@devbig004.ftw2.facebook.com> (raw)
In-Reply-To: <20180806093015.6099ef5c@canb.auug.org.au>
Hello,
On Mon, Aug 06, 2018 at 09:30:15AM +1000, Stephen Rothwell wrote:
> > > So this issue is still happening as of next-20180702. Can you guys
> > > please revert the commit above while working on a better solution?
> >
> > That's fine with me. I'm not very familiar with the process here, does
> > this require anything on my end? And would that require the
> > accompanying patch to be reverted: "ata: ahci: rpm_put port on
> > port_stop to match rpm_get in port_start"? There shouldn't be any
> > problem leaving that one in, but I just want to know before submitting
> > my next patch set.
>
> I am still reverting that commit from linux-next myself. Has this
> issue been fixed some other way, or is it still ongoing?
Hasn't been resolved yet. Reverting from libata/for-4.19.
Thanks.
--
tejun
prev parent reply other threads:[~2018-08-06 17:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 5:52 Naresh Kamboju
2018-06-20 10:29 ` Tony Lindgren
2018-06-20 12:57 ` Samuel Morris
2018-06-20 12:58 ` Roger Quadros
2018-06-20 15:30 ` Samuel Morris
2018-06-21 7:58 ` Roger Quadros
2018-06-21 12:02 ` Rafael J. Wysocki
2018-06-21 14:31 ` Samuel Morris
2018-06-21 14:53 ` Roger Quadros
2018-07-02 9:32 ` Tony Lindgren
2018-07-02 13:31 ` Samuel Morris
2018-07-17 6:08 ` Tony Lindgren
2018-07-17 8:00 ` Stephen Rothwell
2018-07-17 8:03 ` Tony Lindgren
2018-07-18 5:05 ` Keerthy
2018-08-05 23:30 ` Stephen Rothwell
2018-08-06 17:24 ` Tejun Heo [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=20180806172424.GC410235@devbig004.ftw2.facebook.com \
--to=tj@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=olof@lixom.net \
--cc=rafael@kernel.org \
--cc=rogerq@ti.com \
--cc=samorris@lexmark.com \
--cc=sfr@canb.auug.org.au \
--cc=ssantosh@kernel.org \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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
Powered by JetHome