Re: [RESEND PATCH 00/27] update makefiles to use the newer flag variables

From: Michal Marek
Date: Thu Mar 17 2011 - 09:31:42 EST


On 17.3.2011 14:19, Geert Uytterhoeven wrote:
> On Thu, Mar 17, 2011 at 14:15, Michal Marek <mmarek@xxxxxxx> wrote:
>> On Fri, Jan 14, 2011 at 06:12:23AM -0800, matt mooney wrote:
>>> These are the patches that never made their way into the linux-next tree.
>>> I have added all of the acks that came through.
>
>>> m68k: change to new flag variables
>
>> I committed these to kbuild.2.6.git#trivial and will send a pull request
>> to Linus.
>
> JFYI, the m68k one went in last night through the m68k tree.

I did a rebase onto linux-next and back, so that I don't duplicate
patches that have been picked up by subsystem maintainers already. This
is the resulting shortlog, m68k is not there:

matt mooney (25):
kernel: change to new flag variable
arm: change to new flag variables
h8300: change to new flag variable
ia64: change to new flag variables
microblaze: change to new flag variable
mips: change to new flag variable
s390: change to new flag variable
um: change to new flag variables
xtensa: change to new flag variable
fs: change to new flag variable
char: change to new flag variable
dma: change to new flag variable
hwmon: change to new flag variable
ide: change to new flag variable
ieee802154: change to new flag variable
isdn: change to new flag variable
memstick: change to new flag variable
message: change to new flag variable
misc: change to new flag variable
net: change to new flag variable
pps: change to new flag variable
rapidio: change to new flag variable
rtc: change to new flag variable
scsi: change to new flag variable
video: change to new flag variable

I guess I should be more verbose than "thanks, applied" next time :).

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