From: tglx@linutronix.de (Thomas Gleixner)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] imx: gpio interrupt cleanup
Date: Mon, 19 Dec 2011 18:22:28 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.02.1112191821190.3020@ionos> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF176BE92A13@HQMAIL01.nvidia.com>
On Mon, 19 Dec 2011, Stephen Warren wrote:
> Behalf Of Shawn Guo wrote at Thursday, December 08, 2011 7:32 AM:
> > Hi Arnd and Olof,
> >
> > Please consider to pull the series below. I really should have
> > Thomas' ack on Jamie's patch 'irqdomain: export irq_domain_simple_ops
> > for !CONFIG_OF', and Grant's ack on patch 'gpio/mxc: adopt irq_domain
> > in gpio driver'. So this pull request is also asking comments for the
> > path of these patches.
> >
> > Thomas, Grant,
> >
> > Please speak up if you do not want "your" patches to go through arm-soc
> > tree. Thanks.
>
> Thomas,
>
> I'm waiting on the following patch, since I need it to complete a patch
> I'm working on:
>
> > Jamie Iles (1):
> > irqdomain: export irq_domain_simple_ops for !CONFIG_OF
>
> Can you ack it for inclusion in the arm-soc tree, or apply it, so I know
> it's OK to rely on this patch in my work?
If there is nothing else depending on those patches than the arm soc
stuff, them they can go through it with my acked by. Otherwise let me
know, then I pick them up into a branch to pull for you.
Thanks,
tglx
next prev parent reply other threads:[~2011-12-19 17:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 14:32 [GIT PULL] imx: gpio interrupt cleanup Shawn Guo
2011-12-12 10:07 ` Shawn Guo
2011-12-19 17:20 ` Stephen Warren
2011-12-19 17:22 ` Thomas Gleixner [this message]
2011-12-19 17:29 ` Jamie Iles
2011-12-19 17:40 ` Stephen Warren
2011-12-19 18:16 ` Jamie Iles
2011-12-19 21:03 ` Stephen Warren
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=alpine.LFD.2.02.1112191821190.3020@ionos \
--to=tglx@linutronix.de \
--cc=linux-arm-kernel@lists.infradead.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).