From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [BUG] Serial driver broken on migor
Date: Mon, 21 Feb 2011 14:31:46 +0000 [thread overview]
Message-ID: <20110221143146.GA15476@linux-sh.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1102211046270.26977@axis700.grange>
On Mon, Feb 21, 2011 at 06:54:40PM +0900, Alexandre Courbot wrote:
> > As earlier reported on IRC, commit
> > 906b17dc089f7fa87e37a9cfe6ee185efc90e0da locks up migor hard without any
> > output on the serial console. I haven't re-tested the very latest kernel
> > versions, but I don't see any fixes being committed either.
>
> Try applying this little patch:
>
> http://www.spinics.net/lists/linux-sh/msg06875.html
>
> It has not yet been pushed but has been accepted AFAIK. Alternatively,
> your board should boot if you enable earlyprintk.
>
Yes, I have it applied to a working tree already but forgot to push it. Since
then my mail server has been out of comission, so I'm just getting caught up
now. Should be sorted out tomorrow.
prev parent reply other threads:[~2011-02-21 14:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 9:50 [BUG] Serial driver broken on migor Guennadi Liakhovetski
2011-02-21 9:54 ` Alexandre Courbot
2011-02-21 14:31 ` Paul Mundt [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=20110221143146.GA15476@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.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