From: Guan Xuetao <gxt@pku.edu.cn>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: [git pull] Please pull my unicore32 branch
Date: Tue, 10 Jan 2012 10:46:17 +0800 [thread overview]
Message-ID: <1326163577.1782.33.camel@epip-laptop> (raw)
Hi, Linus,
Could you please pull unicore32 branch from my repo:
git://github.com/gxt/linux.git unicore32
Thanks!
Guan Xuetao
The following changes since commit
c99516ca854770000c277b2680a15581c691e18c:
Linus Torvalds (1):
Merge branch 'for-linus' of git://git.kernel.org/.../viro/vfs
are available in the git repository at:
git://github.com/gxt/linux.git unicore32
Guan Xuetao (6):
unicore32: delete specified xlate_dev_mem_ptr
unicore32: add ioremap_nocache definition
rtc-puv3: irq: remove IRQF_DISABLED
i2c-puv3: using module_platform_driver()
rtc-puv3: using module_platform_driver()
rtc-puv3: solve section mismatch in rtc-puv3.c
Kees Cook (1):
unicore32: standardize /proc/iomem "Kernel code" name
Matt Fleming (1):
unicore32: Use set_current_blocked()
Yong Zhang (1):
unicore32: Remove IRQF_DISABLED
Yu Yue (1):
of: add include asm/setup.h in drivers/of/fdt.c
arch/unicore32/include/asm/io.h | 8 +-------
arch/unicore32/kernel/puv3-nb0916.c | 4 ++--
arch/unicore32/kernel/setup.c | 2 +-
arch/unicore32/kernel/signal.c | 15 +++++----------
arch/unicore32/kernel/time.c | 2 +-
drivers/i2c/busses/i2c-puv3.c | 16 ++--------------
drivers/of/fdt.c | 1 +
drivers/rtc/rtc-puv3.c | 22 ++++------------------
8 files changed, 17 insertions(+), 53 deletions(-)
reply other threads:[~2012-01-10 2:53 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=1326163577.1782.33.camel@epip-laptop \
--to=gxt@pku.edu.cn \
--cc=arnd@arndb.de \
--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).