From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [v3.11][v3.12][v3.13][Regression] EISA: Initialize device before its resources
Date: Thu, 16 Jan 2014 13:14:01 -0500 [thread overview]
Message-ID: <52D82169.2000107@canonical.com> (raw)
In-Reply-To: <CAErSpo64e52Vv8bJ54cPcpnZ=OHMaxt2-D6dA4HCrrLnKo1n7g@mail.gmail.com>
On 01/16/2014 01:12 PM, Bjorn Helgaas wrote:
> On Thu, Jan 16, 2014 at 10:53 AM, Joseph Salisbury
> <joseph.salisbury@canonical.com> wrote:
>> Hi Bjorn,
>>
>> A kernel bug was opened against Ubuntu [0]. After a kernel bisect, it
>> was found the following commit introduced this bug:
> Sorry about that, and thanks for the report. Did you mean to include
> URL for the bug?
Yes, sorry about that:
http://pad.lv/1251816
>
>> commit 26abfeed4341872364386c6a52b9acef8c81a81a
>> Author: Bjorn Helgaas <bhelgaas@google.com>
>> Date: Mon Apr 15 14:34:02 2013 -0600
>>
>> EISA: Initialize device before its resources
>>
>> The regression was introduced as of v3.10-rc1.
>>
>> Reverting this commit has resolved the bug. I wanted to get your
>> feedback, since you are the patch author. Should we consider reverting
>> this commit in mainline and the stable trees?
>>
>> Thanks,
>>
>> Joe
>>
next prev parent reply other threads:[~2014-01-16 18:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 17:53 [v3.11][v3.12][v3.13][Regression] EISA: Initialize device before its resources Joseph Salisbury
2014-01-16 18:12 ` Bjorn Helgaas
2014-01-16 18:14 ` Joseph Salisbury [this message]
2014-01-17 17:02 ` Bjorn Helgaas
2014-01-17 19:26 ` Joseph Salisbury
2014-01-17 22:19 ` Bjorn Helgaas
2014-01-18 1:35 ` Joseph Salisbury
2014-01-18 14:37 ` Bjorn Helgaas
2014-01-22 18:00 ` Joseph Salisbury
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=52D82169.2000107@canonical.com \
--to=joseph.salisbury@canonical.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).