All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: Geert Uytterhoeven <geert.uytterhoeven@gmail.com>
Cc: 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:02:44 +1000	[thread overview]
Message-ID: <4A31FD94.5040404@snapgear.com> (raw)
In-Reply-To: <10f740e80906112322k11a518dj3d059b19c086e0c6@mail.gmail.com>

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?)

Currently they are on the branch at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git includes

The easy ones are done, so the re-joining now is not completely
trivial. This set (of 5) is reasonably strait forward though.

Regards
Greg



------------------------------------------------------------------------
Greg Ungerer  --  Principal Engineer        EMAIL:     gerg@snapgear.com
SnapGear Group, McAfee                      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-06-12  7:02 UTC|newest]

Thread overview: 17+ 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  6:22   ` Geert Uytterhoeven
2009-06-12  7:02   ` Greg Ungerer [this message]
2009-06-12 15:34     ` Sam Ravnborg
  -- strict thread matches above, loose matches on Subject: below --
2011-03-16 22:36 Greg Ungerer
2011-03-16 22:36 ` Greg Ungerer
2010-11-04  5:22 Greg Ungerer
2010-11-04  5:22 ` Greg Ungerer
2010-08-18  4:56 Greg Ungerer
2010-08-18  4:56 ` Greg Ungerer
2010-03-23  4:14 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=4A31FD94.5040404@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=akpm@linux-foundation.org \
    --cc=geert.uytterhoeven@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.