linux-kernel - Re: [PATCH 1/4] arm: vt8500: Add support for Wondermedia WM8750/WM8850

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <1357783407.28830.2.camel@gitbox>
Date:	Thu, 10 Jan 2013 15:03:27 +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 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

--
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/