All of lore.kernel.org
 help / color / mirror / Atom feed
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: Fri, 11 Jan 2013 07:32:28 +1300	[thread overview]
Message-ID: <1357842748.6075.4.camel@gitbox> (raw)
In-Reply-To: <201301101021.44238.arnd@arndb.de>

On Thu, 2013-01-10 at 10:21 +0000, Arnd Bergmann wrote:
> On Thursday 10 January 2013, Tony Prisk wrote:
> > On Wed, 2013-01-09 at 21:27 +0000, Arnd Bergmann wrote:
> > > 
> > > > Should patches in pull-requests have Ack'd lines already?
> > 
> > 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 :)
> > 
> 
> Sorry, I think I misunderstood the question then. I meant that if
> you received an Acked-by statement, it should be part of the
> changeset comment by the time you send a pull request.
> 
> There is also the rule that patches need to be reviewed on the
> mailing list before you submit them for inclusion. Like all
> rules, this can be bent a little for patches that are obvious
> correct bug fixes, especially when you are the platform
> maintainer. What you can do here is send the patches out to the
> mailing list without any additional Acks and send the pull
> request as the [PATCH 0/X] mail. We can then look at the
> patches if necessary or just pull in the branch straight away.
> 
> 	Arnd
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel


All makes sense now - thanks.

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: Fri, 11 Jan 2013 07:32:28 +1300	[thread overview]
Message-ID: <1357842748.6075.4.camel@gitbox> (raw)
In-Reply-To: <201301101021.44238.arnd@arndb.de>

On Thu, 2013-01-10 at 10:21 +0000, Arnd Bergmann wrote:
> On Thursday 10 January 2013, Tony Prisk wrote:
> > On Wed, 2013-01-09 at 21:27 +0000, Arnd Bergmann wrote:
> > > 
> > > > Should patches in pull-requests have Ack'd lines already?
> > 
> > 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 :)
> > 
> 
> Sorry, I think I misunderstood the question then. I meant that if
> you received an Acked-by statement, it should be part of the
> changeset comment by the time you send a pull request.
> 
> There is also the rule that patches need to be reviewed on the
> mailing list before you submit them for inclusion. Like all
> rules, this can be bent a little for patches that are obvious
> correct bug fixes, especially when you are the platform
> maintainer. What you can do here is send the patches out to the
> mailing list without any additional Acks and send the pull
> request as the [PATCH 0/X] mail. We can then look at the
> patches if necessary or just pull in the branch straight away.
> 
> 	Arnd
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel


All makes sense now - thanks.

Regards
Tony P


  reply	other threads:[~2013-01-10 18:32 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
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 [this message]
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=1357842748.6075.4.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.