From: H Hartley Sweeten <hartleys@visionengravers.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Grant Likely <grant.likely@secretlab.ca>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Lee Jones <lee.jones@linaro.org>,
Jonas Aaberg <jonas.aberg@stericsson.com>
Subject: RE: [PATCH 02/10] mach-u300: rewrite gpio driver, move to drivers/gpio
Date: Thu, 28 Apr 2011 12:41:38 -0500 [thread overview]
Message-ID: <0D753D10438DA54287A00B027084269764D26C443E@AUSP01VMBX24.collaborationhost.net> (raw)
In-Reply-To: <BANLkTikc7B5J0Z_aiS5kXCxMSxcFrfSRxw@mail.gmail.com>
On Thursday, April 28, 2011 12:08 AM, Linus Walleij wrote:
> 2011/4/27 H Hartley Sweeten <hartleys@visionengravers.com>:
>> The Makefile should probably be reordered, either alphabetically
>> or grouped by type (arch/mmio/i2c/spi/pci/etc) and then
>> alphabetically in order to reduce merge conflicts.
>
> Yes, but if I do that in my patchset I will screw up Grants GPIO tree
> completely, so I prefer that Grant do this. And maybe after pulling
> in my GPIO consolidation tree to his in that case, so we don't get
> undesired collisions. So leaving this for the GPIO maintainer.
This comment was intended for the GPIO maintainer. Sorry for any
confusion.
Regards,
Hartley
WARNING: multiple messages have this Message-ID (diff)
From: hartleys@visionengravers.com (H Hartley Sweeten)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 02/10] mach-u300: rewrite gpio driver, move to drivers/gpio
Date: Thu, 28 Apr 2011 12:41:38 -0500 [thread overview]
Message-ID: <0D753D10438DA54287A00B027084269764D26C443E@AUSP01VMBX24.collaborationhost.net> (raw)
In-Reply-To: <BANLkTikc7B5J0Z_aiS5kXCxMSxcFrfSRxw@mail.gmail.com>
On Thursday, April 28, 2011 12:08 AM, Linus Walleij wrote:
> 2011/4/27 H Hartley Sweeten <hartleys@visionengravers.com>:
>> The Makefile should probably be reordered, either alphabetically
>> or grouped by type (arch/mmio/i2c/spi/pci/etc) and then
>> alphabetically in order to reduce merge conflicts.
>
> Yes, but if I do that in my patchset I will screw up Grants GPIO tree
> completely, so I prefer that Grant do this. And maybe after pulling
> in my GPIO consolidation tree to his in that case, so we don't get
> undesired collisions. So leaving this for the GPIO maintainer.
This comment was intended for the GPIO maintainer. Sorry for any
confusion.
Regards,
Hartley
next prev parent reply other threads:[~2011-04-28 17:41 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 [this message]
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
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=0D753D10438DA54287A00B027084269764D26C443E@AUSP01VMBX24.collaborationhost.net \
--to=hartleys@visionengravers.com \
--cc=grant.likely@secretlab.ca \
--cc=jonas.aberg@stericsson.com \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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 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.