linux-kbuild.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Sam Ravnborg <sam@ravnborg.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>
Subject: Re: [PATCH] m68k,m68knommu: merge header files
Date: Sat, 17 Jan 2009 08:19:29 +1000	[thread overview]
Message-ID: <497107F1.6000208@snapgear.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0901162242010.25319@anakin>


Hi Geert,

Geert Uytterhoeven wrote:
> On Fri, 16 Jan 2009, Sam Ravnborg wrote:
>>>>> 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.
> 
> I pulled from Greg's tree, and built atari_defconfig, multi_defconfig,
> sun3_defconfig. Atari_defconfig runs fine under ARAnyM.
> 
> As I'll be on a business trip to Japan next week, I probably won't be able to
> do a proper follow-up. So Greg, can you put it on your for-next branch and
> send it to Linus if everything goes well?
> 
> Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>

Yep, I can take care of that.

Regards
Greg


------------------------------------------------------------------------
Greg Ungerer  --  Principal Engineer        EMAIL:     gerg@snapgear.com
SnapGear, a McAfee Company                  PHONE:       +61 7 3435 2888
825 Stanley St,                             FAX:         +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia         WEB: http://www.SnapGear.com

      reply	other threads:[~2009-01-16 22:19 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-08 20:58 Merge headerfiles for m68k and m68knommu to arch/m68k/include/asm Sam Ravnborg
2008-12-08 22:53 ` Sam Ravnborg
2008-12-08 23:01 ` Geert Uytterhoeven
2008-12-08 23:26   ` Arnd Bergmann
2008-12-09  5:45     ` Sam Ravnborg
2008-12-09  8:24       ` Geert Uytterhoeven
2008-12-09  9:45         ` Andreas Schwab
2008-12-09 11:02         ` Arnd Bergmann
2008-12-09 18:04           ` Sam Ravnborg
2008-12-11  8:33       ` Geert Uytterhoeven
2008-12-11  9:38         ` Andreas Schwab
2008-12-11 16:48           ` Arnd Bergmann
2008-12-11 20:16         ` Geert Uytterhoeven
2008-12-13 16:16           ` Arnd Bergmann
2008-12-12  5:40         ` Greg Ungerer
2008-12-13 20:46           ` Sam Ravnborg
2008-12-13 20:43     ` Sam Ravnborg
2008-12-09 16:54   ` [uClinux-dev] " Allon Stern
2008-12-09 17:39     ` Geert Uytterhoeven
2008-12-11 15:44       ` Allon Stern
2008-12-12  5:22         ` Greg Ungerer
2008-12-13 20:52 ` Sam Ravnborg
     [not found]   ` <20081213205828.GD27748@uranus.ravnborg.org>
2008-12-14 16:13     ` [PATCH] m68k,m68knommu: merge header files Geert Uytterhoeven
     [not found]     ` <49707AE0.1040803@opengear.com>
2009-01-16 12:57       ` Geert Uytterhoeven
2009-01-16 14:21         ` Greg Ungerer
2009-01-16 14:34           ` Sam Ravnborg
2009-01-16 21:53             ` Geert Uytterhoeven
2009-01-16 22:19               ` Greg Ungerer [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=497107F1.6000208@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=arnd@arndb.de \
    --cc=geert@linux-m68k.org \
    --cc=gerg@uclinux.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=uclinux-dev@uclinux.org \
    --cc=zippel@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;
as well as URLs for NNTP newsgroup(s).