From mboxrd@z Thu Jan  1 00:00:00 1970
From: Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH] m68k,m68knommu: merge header files
Date: Fri, 16 Jan 2009 15:34:29 +0100
Message-ID: <20090116143429.GB22152@uranus.ravnborg.org>
References: <20081208205814.GA22697@uranus.ravnborg.org> <20081213205251.GC27748@uranus.ravnborg.org> <20081213205828.GD27748@uranus.ravnborg.org> <49707AE0.1040803@opengear.com> <Pine.LNX.4.64.0901161354410.18756@anakin> <49709800.70009@snapgear.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <linux-kbuild-owner@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <49709800.70009@snapgear.com>
Sender: linux-kbuild-owner@vger.kernel.org
To: Greg Ungerer <gerg@snapgear.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>, Roman Zippel <zippel@linux-m68k.org>, linux-m68k <linux-m68k@vger.kernel.org>, Greg Ungerer <gerg@uclinux.org>, uclinux-dev <uclinux-dev@uclinux.org>, Arnd Bergmann <arnd@arndb.de>, linux-kbuild <linux-kbuild@vger.kernel.org>
List-Id: linux-m68k@vger.kernel.org

> >>
> >>More review, testing, comments welcome...
> >>Where to from here?
> >
> >I'll pull from it and give it some m68k test builds.
> >After that, you can move it to for-next. If everything's well, it can go to
> >Linus.
> 
> Sounds like a plan.
> 
> 
> >Or should I amend and add my SoB and put it in m68k for-next?
> 
> I am happy to go either way.

For my part I like this to reach mainline ASAP. So whatever suits the
two of you is fine with me.

	Sam