From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux/m68k <linux-m68k@vger.kernel.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: [git pull] m68k updates for 2.6.34
Date: Mon, 29 Mar 2010 20:52:37 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.00.1003292048530.3832@ayla.of.borg> (raw)
Hi Linus,
Please pull to receive 2 more m68k updates for 2.6.34:
- The first one fixes a build problem we started seeing lately,
- The second one corrects struct sigcontext for ColdFire, as I've
accidentally merged the wrong version of a patch for the previous
pull request.
Thanks!
The following changes since commit b72c40949b0f04728f2993a1434598d3bad094ea:
Linus Torvalds (1):
Merge branch 'for-linus' of git://git.kernel.org/.../jbarnes/pci-2.6
are available in the git repository at:
master.kernel.org:/pub/scm/linux/kernel/git/geert/linux-m68k.git for-linus
Geert Uytterhoeven (1):
m68k: Fix asm constraints for atomic_sub_and_test() and atomic_add_negative()
Maxim Kuvyrkov (1):
m68k: Fix `struct sigcontext' for ColdFire
arch/m68k/include/asm/atomic_mm.h | 8 ++++++--
arch/m68k/include/asm/sigcontext.h | 4 +---
2 files changed, 7 insertions(+), 5 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
next reply other threads:[~2010-03-29 18:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 18:52 Geert Uytterhoeven [this message]
2010-04-14 17:56 ` Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2010-02-27 21:13 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.1003292048530.3832@ayla.of.borg \
--to=geert@linux-m68k.org \
--cc=akpm@linux-foundation.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®