From: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
ARM kernel mailing list
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>
Subject: Re: [GIT PULL] USB AUXDATA fix for tegra
Date: Wed, 21 Mar 2012 18:30:24 +0000 [thread overview]
Message-ID: <201203211830.25161.arnd@arndb.de> (raw)
In-Reply-To: <4F6A1AEA.7070505-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
On Wednesday 21 March 2012, Stephen Warren wrote:
> This is my first pull request for Tegra; hopefully it all works out OK!
>
> Note: Nobody has ack'd this change. I'm a maintainer for the files that
> are touched, but I'm not sure if maintainers are supposed to have
> another maintainer ack the change before committing it and sending a
> pull request (in particular for their own changes), or if it's up to
> their discretion?
>
Hi Stephen,
The pull request looks good. There is no need for anyone else to ack
your patches, but you should always post them on the appropriate
mailing lists so people can weigh in if they see something wrong.
I'm currently trying to get the first set of my v3.4 pull requests
out to Linus, so I'll apply this when I'm done with that.
Arnd
next prev parent reply other threads:[~2012-03-21 18:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 18:16 [GIT PULL] USB AUXDATA fix for tegra Stephen Warren
[not found] ` <4F6A1AEA.7070505-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-03-21 18:30 ` Arnd Bergmann [this message]
[not found] ` <201203211830.25161.arnd-r2nGTMty4D4@public.gmane.org>
2012-03-29 18:01 ` 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=201203211830.25161.arnd@arndb.de \
--to=arnd-r2ngtmty4d4@public.gmane.org \
--cc=arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@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