public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: linux@roeck-us•net (Guenter Roeck)
To: linux-arm-kernel@lists•infradead.org
Subject: [Qemu-devel] SCSI bus failures with qemu-arm in kernel 3.8+
Date: Wed, 14 Aug 2013 07:41:04 -0700	[thread overview]
Message-ID: <520B9700.7010105@roeck-us.net> (raw)
In-Reply-To: <CAFEAcA8u_c=seOQ+y44H2Vpefyx4EisiZ-ZqBxuPsyoYjCt3vQ@mail.gmail.com>

On 08/14/2013 05:44 AM, Peter Maydell wrote:
> On 14 August 2013 11:33, Russell King - ARM Linux
> <linux@arm•linux.org.uk> wrote:
>> On Mon, Aug 12, 2013 at 04:04:08PM -0700, Guenter Roeck wrote:
>>> Hacked diff is below. Can I write that up as clean patch and submit it,
>>> or do we need a test on real hardware ?
>>
>> Well, if we want to ensure that it is really correct, the sensible thing
>> to do is to try it on real hardware, otherwise we're risking yet another
>> change to this.
>>
>> Earlier in this thread, some people said that they have the hardware, so
>> it shouldn't be that difficult to get it tested on real stuff.
>
> Yes, I definitely think we should test on the hardware before we
> land yet another change to this PCI code that hasn't really been
> thoroughly tested on anything. I have the board/backplane on my

Agreed.

> desk but it'll be later in the week before I can do the testing
> (currently still messing with uboot config to get it to actually
> boot a kernel).
>

That would be great. Thanks a lot for your help!

Guenter

  parent reply	other threads:[~2013-08-14 14:41 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-11 15:54 SCSI bus failures with qemu-arm in kernel 3.8+ Guenter Roeck
2013-08-11 22:04 ` Russell King - ARM Linux
2013-08-12  0:40   ` Guenter Roeck
2013-08-12 16:24     ` [Qemu-devel] " Peter Maydell
2013-08-12 16:45       ` Russell King - ARM Linux
2013-08-12 17:33         ` Peter Maydell
2013-08-12 20:06           ` Russell King - ARM Linux
2013-08-12 20:49             ` Peter Maydell
2013-08-12 21:21               ` Russell King - ARM Linux
2013-08-12 21:36                 ` Peter Maydell
2013-08-12 22:12                   ` Russell King - ARM Linux
2013-08-12 22:48                     ` Guenter Roeck
2013-08-12 23:04                     ` Guenter Roeck
2013-08-14 10:33                       ` Russell King - ARM Linux
2013-08-14 12:44                         ` Peter Maydell
2013-08-14 12:49                           ` Russell King - ARM Linux
2013-08-14 12:56                             ` Peter Maydell
2013-08-14 14:41                           ` Guenter Roeck [this message]
2013-08-12 17:48         ` Peter Maydell
2013-08-13  8:37         ` Rob Landley
2013-08-13  9:12           ` Peter Maydell
2013-08-13 11:30           ` Russell King - ARM Linux
2013-08-13  3:40       ` Guenter Roeck
2013-08-15 16:45         ` Peter Maydell
2013-08-15 17:54           ` Guenter Roeck
2013-08-15 18:05             ` Peter Maydell
2013-08-15 18:39               ` Guenter Roeck
2013-08-15 20:50               ` Guenter Roeck
2013-08-15 21:49                 ` Peter Maydell
2013-08-15 22:18                   ` Guenter Roeck
2013-08-15 22:23                     ` Peter Maydell
2013-08-15 23:25                       ` Guenter Roeck
2013-08-19 15:26                       ` Guenter Roeck
2013-08-12 19:02     ` Paul Gortmaker
2013-08-12 20:58       ` Peter Maydell

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=520B9700.7010105@roeck-us.net \
    --to=linux@roeck-us$(echo .)net \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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