From: Sam Ravnborg <sam@ravnborg.org>
To: Greg Ungerer <gerg@snapgear.com>
Cc: Geert Uytterhoeven <geert.uytterhoeven@gmail.com>,
linux-kernel@vger.kernel.org, linux-m68k@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [git pull] m68knommu arch fixes
Date: Fri, 12 Jun 2009 17:34:33 +0200 [thread overview]
Message-ID: <20090612153433.GA17129@uranus.ravnborg.org> (raw)
In-Reply-To: <4A31FD94.5040404@snapgear.com>
On Fri, Jun 12, 2009 at 05:02:44PM +1000, Greg Ungerer wrote:
> Hi Geert,
>
> Geert Uytterhoeven wrote:
> >On Fri, Jun 12, 2009 at 03:14, Greg Ungerer<gerg@snapgear.com> wrote:
> >>Please pull to get fixes for the m68knommu arch.
> >
> >>Jaswinder Singh Rajput (1):
> >> headers_check fix: m68k, swab.h
> >
> >Thanks!
>
> No problem :-)
>
>
> >Probably I won't have time to handle and submit any m68k patches
> >during this merge window,
> >so if anyone needs anything to be in 2.6.31, it would be nice if
> >somebody else could take care of
> >it.
>
> I have a few more header file re-merges that I have had sitting
> around for a while, any chance you can review them? (Or maybe I
> just send them to the m68k-linux mailing list?)
Please copy lkml too.
Sam
next prev parent reply other threads:[~2009-06-12 15:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 1:14 [git pull] m68knommu arch fixes Greg Ungerer
2009-06-12 6:22 ` Geert Uytterhoeven
2009-06-12 7:02 ` Greg Ungerer
2009-06-12 15:34 ` Sam Ravnborg [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-16 22:36 Greg Ungerer
2010-11-04 5:22 Greg Ungerer
2010-08-18 4:56 Greg Ungerer
2010-03-23 4:14 Greg Ungerer
2009-10-01 6:16 Greg Ungerer
2009-09-16 0:08 Greg Ungerer
2009-04-23 23:33 Greg Ungerer
2009-01-28 4:59 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=20090612153433.GA17129@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@linux-foundation.org \
--cc=geert.uytterhoeven@gmail.com \
--cc=gerg@snapgear.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.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