mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Greg Ungerer <gerg@uclinux.org>, Greg Ungerer <gerg@snapgear.com>,
	Linux/m68k <linux-m68k@vger.kernel.org>,
	Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: [git pull] m68k updates for 3.3
Date: Thu, 26 Jan 2012 18:39:29 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.00.1201261828070.19382@ayla.of.borg> (raw)

	Hi Linus,

The following changes since commit 3bd9e50b4297b0d85bb86a8f2ade941c0f9c21fd:
  Geert Uytterhoeven (1):
        m68k/mac: Make CONFIG_HEARTBEAT unavailable on Mac

are available in the git repository at:

  ra.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

  - The changeset from Andreas is a critical bugfix (also meant for stable)
    that caused crashes on boot in the wild.
    As it wasn't rebased, it will cause a merge conflict. The correct
    resolution is:

-<<<<<<< HEAD
-               asm volatile ("frestore %0@" : : "a" (&zero) : "memory");
-=======
-               asm volatile (".chip 68k/68881\n\t"
-                             "frestore %0\n\t"
-                             ".chip 68k" : : "m" (zero));
->>>>>>> m68k/for-next = for-linus
+               asm volatile ("frestore %0" : : "m" (zero)

  - The changesets from Finn are fixes for Mac that got silently ignored by
    the respective subsystem maintainers, despite resends.

  - The changeset from me is a postponed cleanup that depended on some
    subsystem trees.

Thanks for pulling!

Andreas Schwab (1):
      m68k: Fix assembler constraint to prevent overeager gcc optimisation

Finn Thain (3):
      macfb: fix black and white modes
      mac_scsi: dont enable mac_scsi irq before requesting it
      mac_esp: rename irq

Geert Uytterhoeven (1):
      m68k/irq: Remove obsolete IRQ_FLG_* definitions

 arch/m68k/atari/config.c      |    8 +++---
 arch/m68k/include/asm/irq.h   |   13 ---------
 arch/m68k/kernel/process_mm.c |    4 +-
 arch/m68k/kernel/process_no.c |    4 +-
 arch/m68k/kernel/traps.c      |   36 +++++++++++-------------
 arch/m68k/mm/cache.c          |    6 ++--
 drivers/scsi/mac_esp.c        |    3 +-
 drivers/scsi/mac_scsi.c       |    6 ----
 drivers/video/macfb.c         |   60 +++++++++++++++++++----------------------
 9 files changed, 57 insertions(+), 83 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

             reply	other threads:[~2012-01-26 17:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-26 17:39 Geert Uytterhoeven [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-01-05 15:12 Geert Uytterhoeven

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=alpine.DEB.2.00.1201261828070.19382@ayla.of.borg \
    --to=geert@linux-m68k.org \
    --cc=akpm@linux-foundation.org \
    --cc=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

all inboxes | Powered by JetHome®