From: Nicolas Pitre <nicolas.pitre@linaro.org>
To: Kyungmin Park <kmpark@infradead.org>
Cc: Shawn Guo <shawn.guo@freescale.com>,
Linus Walleij <linus.walleij@stericsson.com>,
Jonas Aaberg <jonas.aberg@stericsson.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
linux-kernel@vger.kernel.org,
Grant Likely <grant.likely@secretlab.ca>,
Lee Jones <lee.jones@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 02/10] mach-u300: rewrite gpio driver, move to drivers/gpio
Date: Thu, 19 May 2011 23:54:12 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.1105192351360.14430@xanadu.home> (raw)
In-Reply-To: <BANLkTikonewi-fxCxoxx=ARsTs-CPvfoTg@mail.gmail.com>
On Fri, 20 May 2011, Kyungmin Park wrote:
> BTW, how do you think the GPIO interrupt routine. If it uses the
> drivers/gpio drivers, it also cover the gpio interrupt codes at
> drivers/gpio? or separate it?
Let's just do the move for now. I don't think it is worth splitting out
the IRQ code just yet, unless there is a common pattern to be seen
there.
Nicolas
WARNING: multiple messages have this Message-ID (diff)
From: nicolas.pitre@linaro.org (Nicolas Pitre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 02/10] mach-u300: rewrite gpio driver, move to drivers/gpio
Date: Thu, 19 May 2011 23:54:12 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.1105192351360.14430@xanadu.home> (raw)
In-Reply-To: <BANLkTikonewi-fxCxoxx=ARsTs-CPvfoTg@mail.gmail.com>
On Fri, 20 May 2011, Kyungmin Park wrote:
> BTW, how do you think the GPIO interrupt routine. If it uses the
> drivers/gpio drivers, it also cover the gpio interrupt codes at
> drivers/gpio? or separate it?
Let's just do the move for now. I don't think it is worth splitting out
the IRQ code just yet, unless there is a common pattern to be seen
there.
Nicolas
next prev parent reply other threads:[~2011-05-20 4:06 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 13:13 [PATCH 02/10] mach-u300: rewrite gpio driver, move to drivers/gpio Linus Walleij
2011-04-27 13:13 ` Linus Walleij
2011-04-27 18:23 ` H Hartley Sweeten
2011-04-27 18:23 ` H Hartley Sweeten
2011-04-28 7:07 ` Linus Walleij
2011-04-28 7:07 ` Linus Walleij
2011-04-28 7:10 ` Linus Walleij
2011-04-28 7:10 ` Linus Walleij
2011-04-28 17:41 ` H Hartley Sweeten
2011-04-28 17:41 ` H Hartley Sweeten
2011-05-13 14:51 ` Linus Walleij
2011-05-13 14:51 ` Linus Walleij
2011-05-19 8:56 ` Shawn Guo
2011-05-19 8:56 ` Shawn Guo
2011-05-19 12:21 ` Linus Walleij
2011-05-19 12:21 ` Linus Walleij
2011-05-19 13:56 ` Shawn Guo
2011-05-19 13:56 ` Shawn Guo
2011-05-19 19:11 ` Sascha Hauer
2011-05-19 19:11 ` Sascha Hauer
2011-05-19 19:30 ` Nicolas Pitre
2011-05-19 19:30 ` Nicolas Pitre
2011-05-20 3:18 ` Shawn Guo
2011-05-20 3:18 ` Shawn Guo
2011-05-20 3:43 ` Kyungmin Park
2011-05-20 3:43 ` Kyungmin Park
2011-05-20 3:54 ` Nicolas Pitre [this message]
2011-05-20 3:54 ` Nicolas Pitre
2011-05-19 21:18 ` H Hartley Sweeten
2011-05-19 21:18 ` H Hartley Sweeten
2011-05-20 1:50 ` Jamie Iles
2011-05-20 1:50 ` Jamie Iles
2011-05-20 22:07 ` H Hartley Sweeten
2011-05-20 22:07 ` H Hartley Sweeten
2011-05-21 13:03 ` Jamie Iles
2011-05-21 13:03 ` Jamie Iles
2011-05-20 7:01 ` Grant Likely
2011-05-20 7:01 ` Grant Likely
2011-05-20 7:47 ` Linus Walleij
2011-05-20 7:47 ` Linus Walleij
2011-05-19 11:11 ` Barry Song
2011-05-19 11:38 ` Barry Song
2011-05-19 11:38 ` Barry Song
2011-05-19 12:25 ` Linus Walleij
2011-05-19 12:25 ` Linus Walleij
2011-05-19 12:35 ` Barry Song
2011-05-19 12:35 ` Barry Song
2011-05-19 13:17 ` Linus Walleij
2011-05-19 13:17 ` Linus Walleij
2011-05-19 14:05 ` Barry Song
2011-05-19 14:05 ` Barry Song
2011-05-20 6:58 ` Grant Likely
2011-05-20 6:58 ` Grant Likely
2011-05-20 6:52 ` Grant Likely
2011-05-20 6:52 ` Grant Likely
2011-05-20 7:46 ` Linus Walleij
2011-05-20 7:46 ` Linus Walleij
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.00.1105192351360.14430@xanadu.home \
--to=nicolas.pitre@linaro.org \
--cc=grant.likely@secretlab.ca \
--cc=jonas.aberg@stericsson.com \
--cc=kmpark@infradead.org \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawn.guo@freescale.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.