From: Michal Simek <monstr@monstr.eu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Daniel Borkmann <daniel.borkmann@tik.ee.ethz.ch>,
Ariane Keller <ariane.keller@tik.ee.ethz.ch>
Subject: [GIT PULL] arch/microblaze changes for 3.3 rc2
Date: Mon, 30 Jan 2012 09:24:02 +0100 [thread overview]
Message-ID: <4F2653A2.20506@monstr.eu> (raw)
Hi Linus,
please pull this one bug fix for trace code.
Thanks,
Michal
The following changes since commit dcd6c92267155e70a94b3927bce681ce74b80d1f:
Linus Torvalds (1):
Linux 3.3-rc1
are available in the git repository at:
git://git.monstr.eu/linux-2.6-microblaze.git next
Daniel Borkmann (1):
microblaze: generic atomic64 support
arch/microblaze/Kconfig | 1 +
arch/microblaze/include/asm/atomic.h | 1 +
2 files changed, 2 insertions(+), 0 deletions(-)
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
reply other threads:[~2012-01-30 8:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4F2653A2.20506@monstr.eu \
--to=monstr@monstr.eu \
--cc=ariane.keller@tik.ee.ethz.ch \
--cc=daniel.borkmann@tik.ee.ethz.ch \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).