From: Guenter Roeck <linux@roeck-us.net>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH] sh4: Fix serial line access for Linux kernels later than 3.2
Date: Sun, 08 Sep 2013 08:48:47 -0700 [thread overview]
Message-ID: <522C9C5F.30804@roeck-us.net> (raw)
In-Reply-To: <CAFEAcA_=E_vHZyWN-zNekjZrt4Ug2hLzJB17o+08qi8AyE9=Yw@mail.gmail.com>
On 09/08/2013 12:51 AM, Peter Maydell wrote:
> On 8 September 2013 08:39, Guenter Roeck <linux@roeck-us.net> wrote:
>> With Linux kernel version 3.3 or later, qemu fails with the following message:
>>
>> sh_serial: unsupported read from 0x18
>> Aborted
>>
>> Reported-and-analyzed-by: Rob Landley <rob@landley.net>
>> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
>> ---
>> See http://lists.nongnu.org/archive/html/qemu-devel/2012-07/msg03870.html
>> for Rob's analysis of the problem. Unfortunately, the patch never made it
>> into qemu.
>
> Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
>
> since I see from that mail thread that I did check the hardware
> docs. CCing Aurelien as the listed maintainer for sh4.
>
I did run the patch through get_maintainer.pl, but Aurelien was not listed.
Turns out the file is not listed in MAINTAINERS as belonging to sh4.
Should I submit another patch to fix that ?
Guenter
next prev parent reply other threads:[~2013-09-08 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-08 7:39 [Qemu-devel] [PATCH] sh4: Fix serial line access for Linux kernels later than 3.2 Guenter Roeck
2013-09-08 7:51 ` Peter Maydell
2013-09-08 15:48 ` Guenter Roeck [this message]
2013-09-14 4:04 ` Guenter Roeck
2013-09-29 19:12 ` Paolo Bonzini
2013-09-29 19:52 ` [Qemu-devel] [Qemu-trivial] " Michael Tokarev
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=522C9C5F.30804@roeck-us.net \
--to=linux@roeck-us.net \
--cc=aurelien@aurel32.net \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).