From: Grant Likely <grant.likely@secretlab•ca>
To: Mark Brown <broonie@opensource•wolfsonmicro.com>,
Linus Walleij <linus.walleij@linaro•org>
Cc: linux-arch@vger•kernel.org, Grant Likely <grant@secretlab•ca>,
linux-ia64@vger•kernel.org,
Linus Walleij <linus.walleij@stericsson•com>,
Chris Zankel <chris@zankel•net>,
microblaze-uclinux@itee•uq.edu.au, linux@lists•openrisc.net,
linux-kernel@vger•kernel.org, linux-alpha@vger•kernel.org,
sparclinux@vger•kernel.org,
"linuxppc-dev@lists•ozlabs.org list"
<linuxppc-dev@lists•ozlabs.org>
Subject: Re: [PATCH] gpiolib/arches: Centralise bolierplate asm/gpio.h
Date: Fri, 11 May 2012 18:08:53 -0600 [thread overview]
Message-ID: <20120512000853.A96353E0791@localhost> (raw)
In-Reply-To: <20120416081532.GA3238@opensource.wolfsonmicro.com>
On Mon, 16 Apr 2012 09:15:32 +0100, Mark Brown <broonie@opensource•wolfsonmicro.com> wrote:
> On Mon, Apr 16, 2012 at 09:21:58AM +0200, Linus Walleij wrote:
>
> > This looks good but I think we need to page the alpha, ia64, m68k, microblaze,
> > openrisc etc subarch maintainers on this patch so they have their say.
>
> That's why I CCed linux-arch, to get all the architecture maintainers
> included. vger would get upset if I CCed everyone individually.
Meh; it's been long enough. I'll build the major ones and then throw it into linux-next.
g.
--
Grant Likely, B.Sc, P.Eng.
Secret Lab Technologies, Ltd.
prev parent reply other threads:[~2012-05-12 0:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1334483574-3997-1-git-send-email-broonie@opensource.wolfsonmicro.com>
2012-04-16 7:21 ` [PATCH] gpiolib/arches: Centralise bolierplate asm/gpio.h Linus Walleij
2012-04-16 7:53 ` [ORLinux] " Jonas Bonn
2012-04-16 8:15 ` Mark Brown
2012-04-16 8:26 ` Linus Walleij
2012-05-12 0:08 ` Grant Likely [this message]
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=20120512000853.A96353E0791@localhost \
--to=grant.likely@secretlab$(echo .)ca \
--cc=broonie@opensource$(echo .)wolfsonmicro.com \
--cc=chris@zankel$(echo .)net \
--cc=grant@secretlab$(echo .)ca \
--cc=linus.walleij@linaro$(echo .)org \
--cc=linus.walleij@stericsson$(echo .)com \
--cc=linux-alpha@vger$(echo .)kernel.org \
--cc=linux-arch@vger$(echo .)kernel.org \
--cc=linux-ia64@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux@lists$(echo .)openrisc.net \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=microblaze-uclinux@itee$(echo .)uq.edu.au \
--cc=sparclinux@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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