All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-trivial <qemu-trivial@nongnu.org>,
	Peter Maydell <peter.maydell@linaro.org>,
	Rob Landley <rob@landley.net>,
	qemu-devel@nongnu.org, Guenter Roeck <linux@roeck-us.net>
Subject: Re: [Qemu-trivial] [PATCH] sh4: Fix serial line access for Linux kernels later than 3.2
Date: Sun, 29 Sep 2013 23:52:37 +0400	[thread overview]
Message-ID: <52488505.90903@msgid.tls.msk.ru> (raw)
In-Reply-To: <52487BAB.4010703@redhat.com>

29.09.2013 23:12, Paolo Bonzini wrote:
> sh4 is ~orphan so nobody should complain if qemu-trivial picks this up
> as well.
>
> Paolo
>
> Il 14/09/2013 06:04, Guenter Roeck ha scritto:
>> On 09/08/2013 12:39 AM, Guenter Roeck 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>
>>
>> ping ...
>>
>>> ---
>>> 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.

Thanks, applied to the trivial patches queue.

/mjt


WARNING: multiple messages have this Message-ID (diff)
From: Michael Tokarev <mjt@tls.msk.ru>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-trivial <qemu-trivial@nongnu.org>,
	Peter Maydell <peter.maydell@linaro.org>,
	qemu-devel@nongnu.org, Guenter Roeck <linux@roeck-us.net>
Subject: Re: [Qemu-devel] [Qemu-trivial] [PATCH] sh4: Fix serial line access for Linux kernels later than 3.2
Date: Sun, 29 Sep 2013 23:52:37 +0400	[thread overview]
Message-ID: <52488505.90903@msgid.tls.msk.ru> (raw)
In-Reply-To: <52487BAB.4010703@redhat.com>

29.09.2013 23:12, Paolo Bonzini wrote:
> sh4 is ~orphan so nobody should complain if qemu-trivial picks this up
> as well.
>
> Paolo
>
> Il 14/09/2013 06:04, Guenter Roeck ha scritto:
>> On 09/08/2013 12:39 AM, Guenter Roeck 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>
>>
>> ping ...
>>
>>> ---
>>> 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.

Thanks, applied to the trivial patches queue.

/mjt

  reply	other threads:[~2013-09-29 19:52 UTC|newest]

Thread overview: 8+ 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
2013-09-14  4:04 ` Guenter Roeck
2013-09-29 19:12   ` [Qemu-trivial] " Paolo Bonzini
2013-09-29 19:12     ` [Qemu-devel] " Paolo Bonzini
2013-09-29 19:52     ` Michael Tokarev [this message]
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=52488505.90903@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=linux@roeck-us.net \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=rob@landley.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.