From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "Josh Boyer" <jwboyer@fedoraproject.org>,
"Rafał Miłecki" <zajec5@gmail.com>,
"Alexandre Courbot" <gnurou@gmail.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Oops in acpi_gpiochip_add on MacBookPro with Linux v3.14-12042-g69cd9eba3886
Date: Fri, 11 Apr 2014 09:56:24 +0300 [thread overview]
Message-ID: <20140411065624.GB19349@intel.com> (raw)
In-Reply-To: <CACRpkdaBg5KjvksHRB3z2R6KehYcFC=4MEHedfcE6tP4GTh+Qw@mail.gmail.com>
On Thu, Apr 10, 2014 at 08:47:23PM +0200, Linus Walleij wrote:
> On Thu, Apr 10, 2014 at 2:40 PM, Mika Westerberg
> <mika.westerberg@linux.intel.com> wrote:
> > On Thu, Apr 10, 2014 at 08:22:12AM -0400, Josh Boyer wrote:
> >> On Thu, Apr 10, 2014 at 2:50 AM, Rafał Miłecki <zajec5@gmail.com> wrote:
> >> > 2014-04-09 23:09 GMT+02:00 Josh Boyer <jwboyer@fedoraproject.org>:
> >> >> With Linux v3.14-12042-g69cd9eba3886 I get an oops from the bcma
> >> >> module on the MacBookPro 10,2 I have here. This works fine with Linux
> >> >> v3.14-7333-g59ecc26004e7. There have been no changes between those
> >> >> two versions to bcma itself, but the GPIO merge did go in that window.
> >> >> I can attempt to do a bisect tomorrow, but looking over some of the
> >> >> GPIO commits it seems pretty relevant to the ACPI GPIO changes. I'm
> >> >> hoping someone here has an idea on what the issue might be and has
> >> >> some possible things for me to test for fixes.
> >> >
> >> > Bug report: https://lkml.org/lkml/2014/3/24/262
> >> > Patch: https://lkml.org/lkml/2014/3/24/293
> >> > Tested by Sabrina: https://lkml.org/lkml/2014/3/24/304
> >> > (all links are for the same thread).
> >> >
> >> > Now you simply have to find above patch in some git tree :) Not sure
> >> > if it's already in Linus's one.
> >>
> >> Ah, wonderful. I now wish I would have found those in my searching
> >> before doing the bisect. Oh well. For what it's worth, my bisect
> >> landed on the same commit.
> >>
> >> The fix isn't in Linus' tree or linux-next. I'm guessing Mika is
> >> either still on vacation, or hasn't sent out the formal fix yet.
> >
> > No, not on vacation anymore (unfortunately). I did send the formal patch
> > already:
> >
> > https://lkml.org/lkml/2014/3/31/135
> >
> > but it isn't merged to Linus' GPIO tree yet.
>
> I've queued this for fixes!
>
> Will send upstream ASAP.
Thanks!
prev parent reply other threads:[~2014-04-11 6:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 21:09 Oops in acpi_gpiochip_add on MacBookPro with Linux v3.14-12042-g69cd9eba3886 Josh Boyer
2014-04-10 6:50 ` Rafał Miłecki
2014-04-10 12:22 ` Josh Boyer
2014-04-10 12:40 ` Mika Westerberg
[not found] ` <20140410124045.GX19349-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-04-10 12:52 ` Josh Boyer
2014-04-10 13:40 ` Josh Boyer
2014-04-10 18:47 ` Linus Walleij
2014-04-11 6:56 ` Mika Westerberg [this message]
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=20140411065624.GB19349@intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=gnurou@gmail.com \
--cc=jwboyer@fedoraproject.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=zajec5@gmail.com \
/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).