From: Greg Ungerer <gerg@snapgear.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
<linux-m68k@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 12/21] m68k: drop unused Kconfig symbols
Date: Tue, 18 Oct 2011 14:52:11 +1000 [thread overview]
Message-ID: <4E9D05FB.4080607@snapgear.com> (raw)
In-Reply-To: <1318837964.6414.6.camel@x61.thuisdomein>
Hi Paul,
On 17/10/11 17:52, Paul Bolle wrote:
> On Mon, 2011-10-17 at 10:50 +1000, Greg Ungerer wrote:
>> I have no problem with the changes. But it will clash with the
>> reworking of the Kconfig files currently sitting in linux-next
>> for merging in the 3.2 merge window.
>
> So should I put this on hold and see what's needed after those reworked
> Kconfig files are merged in mainline? Or would you prefer to have that
> done beforehand (ie, I'll try to redo this on top of current linux-next
> and get the redone patch in linux-next before the 3.2 merge)?
I won't be too difficult for you to redo your patch. If you can do it
on top of linux-next real soon I can push it into my m68knommu git
tree for-next branch. But it would need to be very soon :-)
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: gerg@snapgear.com
SnapGear Group, McAfee PHONE: +61 7 3435 2888
8 Gardner Close FAX: +61 7 3217 5323
Milton, QLD, 4064, Australia WEB: http://www.SnapGear.com
next prev parent reply other threads:[~2011-10-18 4:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 12:29 [PATCH 12/21] m68k: drop unused Kconfig symbols Paul Bolle
2011-10-17 0:50 ` Greg Ungerer
2011-10-17 7:52 ` Paul Bolle
2011-10-18 4:52 ` Greg Ungerer [this message]
2011-10-18 6:59 ` Paul Bolle
2011-10-18 12:05 ` Greg Ungerer
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=4E9D05FB.4080607@snapgear.com \
--to=gerg@snapgear.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=pebolle@tiscali.nl \
/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