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: <20141029121442.6b6ca116973be0ff8d78c7c2@linux-foundation.org>
Date:	Wed, 29 Oct 2014 12:14:42 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Johan Hovold <johan@...nel.org>
Cc:	Alessandro Zummo <a.zummo@...ertech.it>,
	Tony Lindgren <tony@...mide.com>,
	BenoƮt Cousson <bcousson@...libre.com>,
	Felipe Balbi <balbi@...com>, Lokesh Vutla <lokeshvutla@...com>,
	Guenter Roeck <linux@...ck-us.net>, nsekhar@...com,
	t-kristo@...com, j-keerthy@...com, linux-omap@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
	rtc-linux@...glegroups.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] rtc: omap: add support for pmic_power_en

On Wed, 29 Oct 2014 13:50:05 +0100 Johan Hovold <johan@...nel.org> wrote:

> On Tue, Oct 28, 2014 at 09:36:33AM +0100, Johan Hovold wrote:
> > On Mon, Oct 27, 2014 at 03:40:31PM -0700, Andrew Morton wrote:
> > > On Mon, 27 Oct 2014 09:09:28 +0100 Johan Hovold <johan@...nel.org> wrote:
> 
> > But in general, how do you want to handle updates to a single patch in a
> > series you already have in your tree? Do you prefer a proper
> > incremental-fix patch (with commit message), just an updated single
> > patch, or a resend of the whole series?
> 
> How should I best send the updated patch? Can you just replace the
> current three incremental patches:
> 
> 	rtc-omap-add-support-for-pmic_power_en.patch
> 	rtc-omap-add-support-for-pmic_power_en-v3.patch
> 	rtc-omap-add-support-for-pmic_power_en-v3-fix.patch
> 
> that you have in your tree, with a single new v4 which adds a more
> elaborate comment?

Yep, that works.  I'll almost always turn the new patch into an
incremental, mainly so that I (and others) can see what was changed.
--
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