On Wed, Oct 03, 2012 at 06:49:10AM -0500, Daniel Santos wrote:
> On 10/03/2012 01:44 AM, David Rientjes wrote:
> > On Fri, 28 Sep 2012, Daniel Santos wrote:
> >
> >> Signed-off-by: Daniel Santos <daniel.santos@xxxxxxxxx>
> > After this is folded into the previous patch in the series,
> > "compiler{,-gcc4}.h: Remove duplicate macros", then:
> >
> > Acked-by: David Rientjes <rientjes@xxxxxxxxxx>
> Thanks. I've actually just reversed the patch order per Josh's
> suggestion and added patch comments to it. I can squash them if you
> guys prefer.
>
> Unfortunately, I'm a bit confused as to how I should re-submit these,
> still being new to this project. Patch 1 is already in -mm. Patches 2-3
> have not changed. I've made a correction to patch #4 and reversed the
> order of 5 & 6. And what was 8-10 is now 8-15, as I've completely
> re-done BUILD_BUG_ON. I was planning on just submitting the whole set
> again, is this the correct protocol? If so, should I reply to the
> original [PATCH 0/10] thread or create a new one?
Make your cover letter a reply to the original PATCH 0/10 mail,
generate your patches with git format-patch --subject-prefix=PATCHv2 ,
and include in the cover letter a patch series changelog saying what
changed in v2.
- Josh Triplett
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
