From: linux@prisktech.co.nz (Tony Prisk)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] arm: vt8500: Add support for Wondermedia WM8750/WM8850
Date: Thu, 10 Jan 2013 15:03:27 +1300 [thread overview]
Message-ID: <1357783407.28830.2.camel@gitbox> (raw)
In-Reply-To: <201301092127.05804.arnd@arndb.de>
On Wed, 2013-01-09 at 21:27 +0000, Arnd Bergmann wrote:
> On Wednesday 09 January 2013, Tony Prisk wrote:
> > I'm quite happy to send a pull request if that's what you prefer.
> >
> > Generally people have just taken the patches straight from email, so
> > everytime I've done a pull-request I get a reply back saying the patches
> > have already been applied.
> >
> > Is there some 'rule' around pull-requests vs emailed patches?
>
> Generally, pull requests tend to be less work for us, so I prefer
> them. In particular, when you add a tag description or a signed
> tag, that gives automatically puts nice text into the merge
> changeset.
>
> > Should patches in pull-requests have Ack'd lines already?
>
> Yes.
>
> Arnd
This is what I thought - and the reason I haven't sent a pull-request
for the patch's - I haven't had any Ack's :)
Regards
Tony P
WARNING: multiple messages have this Message-ID (diff)
From: Tony Prisk <linux@prisktech.co.nz>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Olof Johansson <olof@lixom.net>,
vt8500-wm8505-linux-kernel@googlegroups.com, arm@kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/4] arm: vt8500: Add support for Wondermedia WM8750/WM8850
Date: Thu, 10 Jan 2013 15:03:27 +1300 [thread overview]
Message-ID: <1357783407.28830.2.camel@gitbox> (raw)
In-Reply-To: <201301092127.05804.arnd@arndb.de>
On Wed, 2013-01-09 at 21:27 +0000, Arnd Bergmann wrote:
> On Wednesday 09 January 2013, Tony Prisk wrote:
> > I'm quite happy to send a pull request if that's what you prefer.
> >
> > Generally people have just taken the patches straight from email, so
> > everytime I've done a pull-request I get a reply back saying the patches
> > have already been applied.
> >
> > Is there some 'rule' around pull-requests vs emailed patches?
>
> Generally, pull requests tend to be less work for us, so I prefer
> them. In particular, when you add a tag description or a signed
> tag, that gives automatically puts nice text into the merge
> changeset.
>
> > Should patches in pull-requests have Ack'd lines already?
>
> Yes.
>
> Arnd
This is what I thought - and the reason I haven't sent a pull-request
for the patch's - I haven't had any Ack's :)
Regards
Tony P
next prev parent reply other threads:[~2013-01-10 2:03 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-27 23:20 [PATCH 0/4] arm: vt8500: Add new models and remove single-platform Tony Prisk
2012-12-27 23:20 ` Tony Prisk
2012-12-27 23:20 ` [PATCH 1/4] arm: vt8500: Add support for Wondermedia WM8750/WM8850 Tony Prisk
2012-12-27 23:20 ` Tony Prisk
2013-01-09 6:13 ` Tony Prisk
2013-01-09 6:13 ` Tony Prisk
2013-01-09 6:30 ` Olof Johansson
2013-01-09 6:30 ` Olof Johansson
2013-01-09 19:09 ` Tony Prisk
2013-01-09 19:09 ` Tony Prisk
2013-01-09 21:27 ` Arnd Bergmann
2013-01-09 21:27 ` Arnd Bergmann
2013-01-10 2:03 ` Tony Prisk [this message]
2013-01-10 2:03 ` Tony Prisk
2013-01-10 10:21 ` Arnd Bergmann
2013-01-10 10:21 ` Arnd Bergmann
2013-01-10 18:32 ` Tony Prisk
2013-01-10 18:32 ` Tony Prisk
2012-12-27 23:20 ` [PATCH 2/4] arm: vt8500: Remove single platform Kconfig options Tony Prisk
2012-12-27 23:20 ` Tony Prisk
2012-12-27 23:20 ` [PATCH 3/4] arm: vt8500: Convert debug-macro.S to be multiplatform friendly Tony Prisk
2012-12-27 23:20 ` Tony Prisk
2012-12-28 4:21 ` Alexey Charkov
2012-12-28 8:09 ` Tony Prisk
2012-12-28 8:09 ` Tony Prisk
2012-12-27 23:20 ` [PATCH 4/4] arm: vt8500: Remove remaining mach includes Tony Prisk
2012-12-27 23:20 ` Tony Prisk
-- strict thread matches above, loose matches on Subject: below --
2013-01-11 20:12 [PATCH 0/4] arm: vt8500: Add support for Wondermedia WM8750/WM8850 Tony Prisk
2013-01-11 20:12 ` [PATCH 1/4] " Tony Prisk
2013-01-11 20:12 ` Tony Prisk
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=1357783407.28830.2.camel@gitbox \
--to=linux@prisktech.co.nz \
--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 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.