On Mon, Aug 8, 2011 at 3:57 PM, Arend van Spriel <arend@xxxxxxxxxxxx> wrote: > Before and during the 3.1 merge window three patch series were posted. Feedback > from Dan Carpenter learned that some of the patches did not apply after 3.1 > merges. Therefor the series are resubmitted here with some changes as described > below. > > [PATCHv2 01/82] fixes a compilation error due to missing <linux/io.h> include > since 3.1-rc1. > > Series "[PATCH 00/35] staging: brcm80211: code cleanup and bugfix": > [PATCH 17/35] has been merged with later patch to remove checkpatch warning. > [PATCH 33/35] was removed as it caused regression for brcmfmac driver. > > Series "[PATCH 00/19] checkpatch changes and brcmfmac cleanup" > Resubmitted as before. > > Series "[PATCH 00/29] staging: brcm80211: cleanup checkpatch warnings" > [PATCH 09/29] has been rephrased to apropriately describe what changed. > [PATCH 13/29] was merged with [PATCH 17/35] from the first series. > > [PATCHv2 80/82] fixes a compiler warning for ARM platform since 3.1-rc1. > > Arend Van Spriel (1): > staging: brcm80211: fix compile error on non-x86 archs since 3.0 > kernel > Personally, I have no broadcom wifi-card. First of all, it won't hurt to add some URLs (for example <marc.info>) for your previous postings, so interested people can easily follow. Just some suggestions for subject-prefix: 1. Drop "staging" from subject-lines? Saves some chars. 2. Using "staging/brcm80211" would also save some chars (and is more common to me). 3. "PATCH v2" should be with a space? 4. Something like "for-3.1" would clearly indicate for which kernel-release this mega-series is for (also "staging" could be dropped as it is known where the driver is managed) $ git format-patch --signoff --cover-letter --subject-prefix="PATCH v2 for-3.1" -82 (or whatever $FIRST..$LAST) - Sedat - _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
