From: Michal Marek <mmarek@suse.cz>
To: Greg Ungerer <gerg@snapgear.com>, Greg Ungerer <gerg@uclinux.org>,
Andrew Morton <akpm@linux-foundation.org>,
David Howells <dhowells@redhat.com>,
Tim Abbott <tabbott@ksplice.com>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH 08/20] m68knommu: change to new flag variables
Date: Thu, 30 Sep 2010 20:51:18 +0000 [thread overview]
Message-ID: <4CA4F846.8070704@suse.cz> (raw)
In-Reply-To: <20100929231521.GA21930@haskell.muteddisk.com>
On 30.9.2010 01:15, matt mooney wrote:
> Okay, if anybody else asks, I will definitely ask them kindly to pick them
> up. There are, however, some patches that will need to go through the kbuild
> tree because some maintainers have already acked the patches and not picked them
> up.
You can ask them to apply the patches :).
I will wait a couple more weeks, and then I will resend to you and the
> kbuild list with all acks added.
OK.
Michal
WARNING: multiple messages have this Message-ID (diff)
From: Michal Marek <mmarek@suse.cz>
To: Greg Ungerer <gerg@snapgear.com>, Greg Ungerer <gerg@uclinux.org>,
Andrew Morton <akpm@linux-foundation.org>,
David Howells <dhowells@redhat.com>,
Tim Abbott <tabbott@ksplice.com>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH 08/20] m68knommu: change to new flag variables
Date: Thu, 30 Sep 2010 22:51:18 +0200 [thread overview]
Message-ID: <4CA4F846.8070704@suse.cz> (raw)
In-Reply-To: <20100929231521.GA21930@haskell.muteddisk.com>
On 30.9.2010 01:15, matt mooney wrote:
> Okay, if anybody else asks, I will definitely ask them kindly to pick them
> up. There are, however, some patches that will need to go through the kbuild
> tree because some maintainers have already acked the patches and not picked them
> up.
You can ask them to apply the patches :).
I will wait a couple more weeks, and then I will resend to you and the
> kbuild list with all acks added.
OK.
Michal
next prev parent reply other threads:[~2010-09-30 20:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 6:50 [PATCH 08/20] m68knommu: change to new flag variables matt mooney
2010-09-23 6:50 ` matt mooney
2010-09-28 6:41 ` Greg Ungerer
2010-09-28 6:41 ` Greg Ungerer
2010-09-28 7:16 ` matt mooney
2010-09-28 7:16 ` matt mooney
2010-09-28 13:22 ` Greg Ungerer
2010-09-28 13:22 ` Greg Ungerer
2010-09-29 14:36 ` Michal Marek
2010-09-29 14:36 ` Michal Marek
2010-09-29 23:15 ` matt mooney
2010-09-29 23:15 ` matt mooney
2010-09-30 20:51 ` Michal Marek [this message]
2010-09-30 20:51 ` Michal Marek
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=4CA4F846.8070704@suse.cz \
--to=mmarek@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=gerg@snapgear.com \
--cc=gerg@uclinux.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tabbott@ksplice.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.