public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Greg Ungerer <gerg@snapgear.com>
Cc: uClinux development list <uclinux-dev@uclinux.org>,
	Greg Ungerer <gerg@uclinux.org>,
	Linux/m68k <linux-m68k@vger.kernel.org>,
	Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [uClinux-dev] [PATCH] m68k: Unify arch/m68k/include/asm/unistd.h
Date: Sun, 1 Feb 2009 23:39:11 +0100	[thread overview]
Message-ID: <20090201223911.GA30935@uranus.ravnborg.org> (raw)
In-Reply-To: <498599A6.7080202@snapgear.com>

On Sun, Feb 01, 2009 at 10:46:30PM +1000, Greg Ungerer wrote:
> Hi Geert,
> 
> Geert Uytterhoeven wrote:
> >>From b708bab9dbc93bc80bd06c9222ab34530736f737 Mon Sep 17 00:00:00 2001
> >From: Geert Uytterhoeven <geert@linux-m68k.org>
> >Date: Thu, 29 Jan 2009 21:21:40 +0100
> >Subject: [PATCH] m68k: Unify arch/m68k/include/asm/unistd.h
> >
> >arch/m68k/include/asm/unistd_{no,mm}.h are identical, except for whitespace
> >differences, so unify them.
> >
> >Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
> >---
> 
> Looks good to me.
> 
> I started down the track of merging similar headers on Friday too.
> 
> So far I have about 12 or so for review at in the git tree below.
> (One of which is exactly this unistd.h merge :-)  Still plenty of
> easy merges amongst the other files too...

Glad to see this. When we merged sparc we likewise identified
more that was relatively easy to merge than at least I initially anticipated.

I am not able to help at least not the next month or so.
After that I hope to be able to have mroe Linux time again.

	Sam

  reply	other threads:[~2009-02-01 22:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-01 10:15 [PATCH] m68k: Unify arch/m68k/include/asm/unistd.h Geert Uytterhoeven
2009-02-01 12:46 ` [uClinux-dev] " Greg Ungerer
2009-02-01 22:39   ` Sam Ravnborg [this message]
2009-02-02 21:46   ` Geert Uytterhoeven
2009-02-03  6:36     ` Greg Ungerer
2009-02-02 21:47   ` Geert Uytterhoeven
2009-02-03  6:41     ` 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=20090201223911.GA30935@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=gerg@snapgear.com \
    --cc=gerg@uclinux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=uclinux-dev@uclinux.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