From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: earlycon issues in -next with amba-pl011 updates
Date: Fri, 4 Sep 2015 12:13:18 +0100 [thread overview]
Message-ID: <20150904111318.GF21084@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20150904110651.GE4818@arm.com>
On Fri, Sep 04, 2015 at 12:06:52PM +0100, Will Deacon wrote:
> On Thu, Sep 03, 2015 at 05:08:53PM +0100, Marc Zyngier wrote:
> > On 03/09/15 16:52, Greg Kroah-Hartman wrote:
> > > On Thu, Sep 03, 2015 at 11:23:15AM +0100, Marc Zyngier wrote:
> > >> So -next has now been broken for a while on a number of ARM platforms
> > >> because of this (they simply cannot boot), and no progress has been made
> > >> towards resolving this problem.
> > >>
> > >> Can we please drop this series (at least commits 7b753f3 and following)
> > >> from -next until is has been reworked and reviewed?
> > >
> > > I don't have any patches in my -next tree, everything is in Linus's tree
> > > now. So if I've missed something, or need to revert something, please
> > > let me know specifcally what to do.
> >
> > Gahhh... Given that there is no obvious fix, that the discussion has
> > stalled and that the author of the series is apparently away, the
> > following patches should be reverted:
> >
> > 8cd90e50d140 uart: pl011: Add support to ZTE ZX296702 uart
> > 09dcc7dfc05b uart: pl011: Improve LCRH register access decision
> > 2c096a9eedc6 uart: pl011: Introduce register look up table
> > 7b753f318d14 uart: pl011: Introduce register accessor
> > 534e14e2293d uart: pl011: Rename regs with enumeration
> >
> > (7b753f318d14 being the one breaking everything, but it makes more sense
> > to revert the whole series until it is properly fixed and reviewed).
>
> For the reverts (git revert 534e14e2293d~1..8cd90e50d140):
>
> Acked-by: Will Deacon <will.deacon@arm.com>
> Tested-by: Will Deacon <will.deacon@arm.com>
>
> We can discuss what could've and should've happened 'til we're blue in
> the face but, in the meantime, I'd like my serial console back.
>
> Greg -- any chance you could send these for -rc1, please?
Given the number of reviews the patches went through, I eventually came
to the conclusion that it would be far better if I were to write the
set of patches for the driver - but I haven't had a slot to do that.
I basically stopped reviewing them because I decided it wasn't worth
spending the time anymore on the series. That wasn't an implicit
"I'm happy with the patch set" but more a "I've given up with this
patch set, it's still not up to scratch."
--
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-09-04 11:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 23:23 earlycon issues in -next with amba-pl011 updates Leif Lindholm
2015-08-11 0:31 ` Peter Hurley
2015-08-11 10:07 ` Leif Lindholm
2015-08-11 12:40 ` Russell King - ARM Linux
2015-08-17 16:04 ` Peter Hurley
2015-08-11 1:48 ` Jun Nie
2015-09-03 10:23 ` Marc Zyngier
2015-09-03 15:52 ` Greg Kroah-Hartman
2015-09-03 16:08 ` Marc Zyngier
2015-09-03 17:49 ` Peter Hurley
2015-09-03 17:53 ` Greg Kroah-Hartman
2015-09-03 18:03 ` Peter Hurley
2015-09-03 18:16 ` Marc Zyngier
2015-09-03 18:21 ` Peter Hurley
2015-09-03 18:00 ` Marc Zyngier
2015-09-03 18:15 ` Peter Hurley
2015-09-04 11:06 ` Will Deacon
2015-09-04 11:13 ` Russell King - ARM Linux [this message]
2015-09-05 14:54 ` Jun Nie
2015-09-04 16:15 ` Greg Kroah-Hartman
2015-09-04 16:16 ` Will Deacon
2015-09-05 14:42 ` Jun Nie
2015-09-09 19:54 ` Greg Kroah-Hartman
[not found] ` <CAKU3ayWkXxmF1cp=fOAL6kNKY3wY1u=XhPROKiLqkx4oZ9xZ0g@mail.gmail.com>
2015-09-16 0:54 ` Jun Nie
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=20150904111318.GF21084@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.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;
as well as URLs for NNTP newsgroup(s).