From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: Linus Walleij
<linus.walleij-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>
Subject: Re: [PATCH] gpio: tegra: Fix build issue due to irq_domain rework.
Date: Fri, 24 Feb 2012 16:29:42 -0700 [thread overview]
Message-ID: <20120224232942.GL25293@ponder.secretlab.ca> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF17BD8BCE0C-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
On Fri, Feb 24, 2012 at 03:12:37PM -0800, Stephen Warren wrote:
> Stephen Warren wrote at Monday, February 13, 2012 4:21 PM:
> > Commit 7da5a66 "irq_domain: Remove 'new' irq_domain in favour of the
> > ppc one" changed the set of available irq domain APIs. Update the Tegra
> > GPIO driver to account for those changes, to solve a build break.
>
> Grant, Linus,
>
> Could this please be checked in; linux-next since about Feb 6th doesn't
> build for Tegra without it.
This doesn't apply against the gpio tree since I didn't pick up the DT patches.
It looks like Olof did. (3391811c & 6f74dc9bc). The irq_domain branch is
stable now, so it can be merged into the arm-soc tree before applying this
patch.
g.
next prev parent reply other threads:[~2012-02-24 23:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 23:21 [PATCH] gpio: tegra: Fix build issue due to irq_domain rework Stephen Warren
2012-02-24 23:12 ` Stephen Warren
[not found] ` <74CDBE0F657A3D45AFBB94109FB122FF17BD8BCE0C-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2012-02-24 23:29 ` Grant Likely [this message]
[not found] ` <20120224232942.GL25293-e0URQFbLeQY2iJbIjFUEsiwD8/FfD2ys@public.gmane.org>
2012-02-26 21:23 ` Olof Johansson
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=20120224232942.GL25293@ponder.secretlab.ca \
--to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
--cc=linus.walleij-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org \
--cc=swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.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).