public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: matt mooney <mfm@muteddisk.com>,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH 00/27] update makefiles to use the newer flag variables
Date: Thu, 17 Mar 2011 14:31:33 +0100	[thread overview]
Message-ID: <4D820D35.600@suse.cz> (raw)
In-Reply-To: <AANLkTikiBgigwOkXbYpTqr-4ihVYrmYB49pvh7k2toLz@mail.gmail.com>

On 17.3.2011 14:19, Geert Uytterhoeven wrote:
> On Thu, Mar 17, 2011 at 14:15, Michal Marek <mmarek@suse.cz> 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

      reply	other threads:[~2011-03-17 13:31 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-14 14:12 [RESEND PATCH 00/27] update makefiles to use the newer flag variables matt mooney
2011-01-14 14:12 ` [RESEND PATCH 01/27] kernel: change to new flag variable matt mooney
2011-01-14 14:12 ` [RESEND PATCH 02/27] alpha: change to new flag variables matt mooney
2011-01-14 14:12 ` [RESEND PATCH 03/27] arm: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 04/27] h8300: change to new flag variable matt mooney
2011-01-14 14:12 ` [RESEND PATCH 05/27] ia64: change to new flag variables matt mooney
2011-01-14 14:12 ` [RESEND PATCH 06/27] m68k: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 07/27] microblaze: change to new flag variable matt mooney
2011-01-14 14:12 ` [RESEND PATCH 08/27] mips: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 09/27] s390: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 10/27] um: change to new flag variables matt mooney
2011-01-14 14:12 ` [RESEND PATCH 11/27] xtensa: change to new flag variable matt mooney
2011-01-14 14:12 ` [RESEND PATCH 12/27] fs: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 13/27] char: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 14/27] dma: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 15/27] hwmon: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 16/27] ide: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 17/27] ieee802154: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 18/27] isdn: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 19/27] memstick: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 20/27] message: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 21/27] misc: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 22/27] net: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 23/27] pps: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 24/27] rapidio: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 25/27] rtc: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 26/27] scsi: " matt mooney
2011-01-14 14:12 ` [RESEND PATCH 27/27] video: " matt mooney
2011-03-17 13:15 ` [RESEND PATCH 00/27] update makefiles to use the newer flag variables Michal Marek
2011-03-17 13:19   ` Geert Uytterhoeven
2011-03-17 13:31     ` Michal Marek [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D820D35.600@suse.cz \
    --to=mmarek@suse.cz \
    --cc=geert@linux-m68k.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfm@muteddisk.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox