[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-m68k
Subject:    [git pull] m68k updates for 2.6.36
From:       Geert Uytterhoeven <geert () linux-m68k ! org>
Date:       2010-08-10 19:02:53
Message-ID: alpine.DEB.2.00.1008102055280.17281 () ayla ! of ! borg
[Download RAW message or body]

	Hi Linus,

Please pull to receive the m68k updates for 2.6.36.

BTW, according to your comments for Jens, this time I did not rebase my
for-linus branch on top of your tree-of-the-moment, but on top of v2.6.35.
But I'm still wondering if this really is better? I never merge anything on
my for-linus branch, and I always verify that my (rebased on every stable
and rc release) m68k-queue branch gives an identical tree to my (merged
on every stable and rc release) private development branch.

The following changes since commit 9fe6206f400646a2322096b56c59891d530e8d51:
  Linus Torvalds (1):
        Linux 2.6.35

are available in the git repository at:

  master.kernel.org:/pub/scm/linux/kernel/git/geert/linux-m68k.git for-linus
  git://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git for-linus

Andrea Gelmini (1):
      arch/m68k/sun3/leds.c: Checkpatch cleanup

Finn Thain (2):
      m68k/mac: Add color classic ii support
      m68k/mac: Fix RTC on PMU machines

Geert Uytterhoeven (2):
      zorro: BKL removal
      zorro: Fix reading of proc/bus/zorro/* in small chunks

 arch/m68k/mac/config.c |    9 +++++++++
 arch/m68k/mac/misc.c   |    6 +++---
 arch/m68k/sun3/leds.c  |    4 ++--
 drivers/zorro/proc.c   |   17 +++++++++--------
 4 files changed, 23 insertions(+), 13 deletions(-)

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
[prev in list] [next in list] [prev in thread] [next in thread]