From: Paul Bolle <pebolle@tiscali.nl>
To: Greg Ungerer <gerg@snapgear.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 12/21] m68k: drop unused Kconfig symbols
Date: Tue, 18 Oct 2011 08:59:55 +0200 [thread overview]
Message-ID: <1318921195.6414.15.camel@x61.thuisdomein> (raw)
In-Reply-To: <4E9D05FB.4080607@snapgear.com>
On Tue, 2011-10-18 at 14:52 +1000, Greg Ungerer wrote:
> If you can do it on top of linux-next real soon I can push it into my
> m68knommu git tree for-next branch.
So, to be sure, that would be on top of
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
master, wouldn't it?
Paul Bolle
next prev parent reply other threads:[~2011-10-18 6:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1318595371.6132.70.camel@x61.thuisdomein>
2011-10-17 0:50 ` [PATCH 12/21] m68k: drop unused Kconfig symbols Greg Ungerer
2011-10-17 7:52 ` Paul Bolle
[not found] ` <1318837964.6414.6.camel@x61.thuisdomein>
2011-10-18 4:52 ` Greg Ungerer
[not found] ` <4E9D05FB.4080607@snapgear.com>
2011-10-18 6:59 ` Paul Bolle [this message]
2011-10-18 12:05 ` Greg Ungerer
2011-10-14 12:29 Paul Bolle
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=1318921195.6414.15.camel@x61.thuisdomein \
--to=pebolle@tiscali.nl \
--cc=geert@linux-m68k.org \
--cc=gerg@snapgear.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
/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