From: Mason <slash.tmp@free.fr>
To: Peter Hurley <peter@hurleysoftware.com>,
linux-serial <linux-serial@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>
Cc: Sebastian Frias <sf84@laposte.net>,
Mans Rullgard <mans@mansr.com>, Jean Delvare <jdelvare@suse.de>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: Problem with 4.6-rc2
Date: Mon, 18 Apr 2016 20:46:18 +0200 [thread overview]
Message-ID: <57152B7A.1070202@free.fr> (raw)
In-Reply-To: <5715279B.9060806@free.fr>
On 18/04/2016 20:29, Mason wrote:
> On 18/04/2016 20:06, Peter Hurley wrote:
>
>> On 04/18/2016 09:24 AM, Mason wrote:
>>
>>> I'm running into this panic. I will take a closer look tomorrow.
>>> Any ideas?
>>
>> commit 8d2acdb9fc3a544ab0442634531834d6007b5467
>> Author: Jean Delvare <jdelvare@suse.de>
>> Date: Mon Feb 22 09:00:39 2016 +0100
>>
>> serial: 8250: Add hardware dependency to RT288X option
>>
>> Kconfig option SERIAL_8250_RT288X seems to be only relevant on MIPS
>> platforms, so do not present it on other architectures, unless
>> build-testing.
>>
>> Signed-off-by: Jean Delvare <jdelvare@suse.de>
>> Cc: Mans Rullgard <mans@mansr.com>
>> Cc: Jiri Slaby <jslaby@suse.com>
>> Acked-by: John Crispin <blogic@openwrt.org>
>> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>>
>>
>> Not sure why Greg picked this up over my objections though
>
> Peter,
>
> Thanks for pointing out the problem.
>
> Greg,
>
> My ARM-based SoC uses this hardware (Palmchip BK-3103) and it
> now panics on boot.
>
> Can we revert 8d2acdb9fc3a in time for v4.7?
Errr... I meant v4.6 final.
Regards.
next prev parent reply other threads:[~2016-04-18 18:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 16:24 Problem with 4.6-rc2 Mason
2016-04-18 18:06 ` Peter Hurley
2016-04-18 18:29 ` Mason
2016-04-18 18:46 ` Mason [this message]
2016-04-18 19:23 ` Jean Delvare
2016-04-18 19:58 ` Mason
2016-04-19 6:21 ` Greg KH
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=57152B7A.1070202@free.fr \
--to=slash.tmp@free.fr \
--cc=gregkh@linuxfoundation.org \
--cc=jdelvare@suse.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=mans@mansr.com \
--cc=peter@hurleysoftware.com \
--cc=sf84@laposte.net \
/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).