public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: torvalds@linux-foundation.org
Cc: gerg@uclinux.org, linux-kernel@vger.kernel.org,
	linux-m68k@vger.kernel.org
Subject: [git pull] m68knommu arch fixes
Date: Wed, 18 Aug 2010 14:56:40 +1000	[thread overview]
Message-ID: <201008180456.o7I4uekp031013@goober.internal.moreton.com.au> (raw)


Hi Linus,

Can you please pull the m68knommu git tree, for-linus branch.
A couple of minor bug fixes here for the m68knommu arch.

Thanks
Greg



The following changes since commit da5cabf80e2433131bf0ed8993abc0f7ea618c73:
  Linus Torvalds (1):
        Linux 2.6.36-rc1

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git for-linus

Greg Ungerer (1):
      m68knommu: include sched.h in ColdFire/SPI driver

Jate Sujjavanich (1):
      m68knommu: arch/m68k/include/asm/ide.h fix for nommu

Kulikov Vasiliy (1):
      m68knommu: formatting of pointers in printk()

 arch/m68k/include/asm/ide.h     |   13 +++++++++++--
 arch/m68knommu/kernel/process.c |   10 +++++-----
 drivers/spi/coldfire_qspi.c     |    1 +
 3 files changed, 17 insertions(+), 7 deletions(-)

             reply	other threads:[~2010-08-18  4:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-18  4:56 Greg Ungerer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-03-16 22:36 [git pull] m68knommu arch fixes Greg Ungerer
2010-11-04  5:22 Greg Ungerer
2010-03-23  4:14 Greg Ungerer
2009-10-01  6:16 Greg Ungerer
2009-09-16  0:08 Greg Ungerer
2009-06-12  1:14 Greg Ungerer
2009-06-12  6:22 ` Geert Uytterhoeven
2009-06-12  7:02   ` Greg Ungerer
2009-06-12 15:34     ` Sam Ravnborg
2009-04-23 23:33 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=201008180456.o7I4uekp031013@goober.internal.moreton.com.au \
    --to=gerg@snapgear.com \
    --cc=gerg@uclinux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=torvalds@linux-foundation.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