From: Jeremy Linton <jlinton@tributary.com>
To: Grant Likely <grant.likely@linaro.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Jeremy Linton <lintonrjeremy@gmail.com>
Cc: <robherring2@gmail.com>, <devicetree@vger.kernel.org>,
<linuxppc-dev@lists.ozlabs.org>, <paulus@samba.org>
Subject: Re: [PATCH] Fix pSeries boot failure, by returning interrupt controller node when an interrupt-map property doesn't exist
Date: Tue, 30 Jun 2015 13:14:48 -0500 [thread overview]
Message-ID: <5592DC98.8070805@tributary.com> (raw)
In-Reply-To: <20150630160156.7010DC405A7@trevor.secretlab.ca>
On 6/30/2015 11:01 AM, Grant Likely wrote:
> Merged, thanks.
Thanks!
> Jeremy, please check your mailer configuration. The patch was mangled
> and would not apply. I had to fix it up manually.
Sorry about that, I will see about creating a better setup (aka not gmail/web
client) for patches I send from home.
> Also, does this patch need to be backported into stable? What commit
> introduced this bug, and which kernel does it first appear in?
I didn't bisect the problem so i'm not 100% sure, but I think the commit that
caused this was 2361613206e66ce59cc0e08efa8d98ec15b84ed1 AKA 3.13. For me I
don't need stable, I just pulled the machine forward on a whim in order to build
some other things. I will try to do that more frequently due to the fact that
the bug existed for a little over a year..
WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Linton <jlinton-WMdfZNuR64nqlBn2x/YWAg@public.gmane.org>
To: Grant Likely
<grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Benjamin Herrenschmidt
<benh-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>,
Jeremy Linton
<lintonrjeremy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
paulus-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org
Subject: Re: [PATCH] Fix pSeries boot failure, by returning interrupt controller node when an interrupt-map property doesn't exist
Date: Tue, 30 Jun 2015 13:14:48 -0500 [thread overview]
Message-ID: <5592DC98.8070805@tributary.com> (raw)
In-Reply-To: <20150630160156.7010DC405A7-WNowdnHR2B42iJbIjFUEsiwD8/FfD2ys@public.gmane.org>
On 6/30/2015 11:01 AM, Grant Likely wrote:
> Merged, thanks.
Thanks!
> Jeremy, please check your mailer configuration. The patch was mangled
> and would not apply. I had to fix it up manually.
Sorry about that, I will see about creating a better setup (aka not gmail/web
client) for patches I send from home.
> Also, does this patch need to be backported into stable? What commit
> introduced this bug, and which kernel does it first appear in?
I didn't bisect the problem so i'm not 100% sure, but I think the commit that
caused this was 2361613206e66ce59cc0e08efa8d98ec15b84ed1 AKA 3.13. For me I
don't need stable, I just pulled the machine forward on a whim in order to build
some other things. I will try to do that more frequently due to the fact that
the bug existed for a little over a year..
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-06-30 18:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 23:50 [PATCH] Fix pSeries boot failure, by returning interrupt controller node when an interrupt-map property doesn't exist Jeremy Linton
2015-06-29 23:50 ` Jeremy Linton
2015-06-30 3:23 ` Benjamin Herrenschmidt
2015-06-30 3:23 ` Benjamin Herrenschmidt
2015-06-30 16:01 ` Grant Likely
2015-06-30 16:01 ` Grant Likely
2015-06-30 18:14 ` Jeremy Linton [this message]
2015-06-30 18:14 ` Jeremy Linton
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=5592DC98.8070805@tributary.com \
--to=jlinton@tributary.com \
--cc=benh@kernel.crashing.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=lintonrjeremy@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=robherring2@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 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.