lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1357842748.6075.4.camel@gitbox>
Date:	Fri, 11 Jan 2013 07:32:28 +1300
From:	Tony Prisk <linux@...sktech.co.nz>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Olof Johansson <olof@...om.net>,
	vt8500-wm8505-linux-kernel@...glegroups.com, arm@...nel.org,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 1/4] arm: vt8500: Add support for Wondermedia
 WM8750/WM8850

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@...ts.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel


All makes sense now - thanks.

Regards
Tony P

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ