From: Mike Frysinger <vapier@gentoo.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, uclinux-dist-devel@blackfin.uclinux.org
Subject: Pull request blackfin.git (for-linus branch)
Date: Fri, 4 Mar 2011 03:58:22 -0500 [thread overview]
Message-ID: <1299229102-26414-1-git-send-email-vapier@gentoo.org> (raw)
The following changes since commit b65a0e0c84cf489bfa00d6aa6c48abc5a237100f:
Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/security-testing-2.6 (2011-03-03 15:48:01 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/vapier/blackfin.git for-linus
Mike Frysinger (2):
Blackfin: outs[lwb]: make sure count is greater than 0
Blackfin: iflush: update anomaly 05000491 workaround
arch/blackfin/lib/outs.S | 16 ++++++++++++----
arch/blackfin/mach-common/cache.S | 2 ++
2 files changed, 14 insertions(+), 4 deletions(-)
next reply other threads:[~2011-03-04 8:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 8:58 Mike Frysinger [this message]
2011-03-04 8:58 ` [PATCH 1/2] Blackfin: outs[lwb]: make sure count is greater than 0 Mike Frysinger
2011-03-04 8:58 ` [PATCH 2/2] Blackfin: iflush: update anomaly 05000491 workaround Mike Frysinger
-- strict thread matches above, loose matches on Subject: below --
2011-10-26 8:34 [PATCH 00/15] Blackfin updates for 3.2-rc0 Mike Frysinger
2011-10-26 8:36 ` Pull request blackfin.git (for-linus branch) Mike Frysinger
2011-07-23 5:29 [PATCH 00/43] Blackfin updates for v3.1-rc0 Mike Frysinger
2011-07-23 14:05 ` Pull request blackfin.git (for-linus branch) Mike Frysinger
2011-06-03 17:04 Mike Frysinger
2011-05-29 2:38 [PATCH 0/8] (some) Blackfin updates for 2.6.40 Mike Frysinger
2011-05-29 2:40 ` Pull request blackfin.git (for-linus branch) Mike Frysinger
2011-05-25 18:44 [PATCH 00/37] Blackfin updates for 2.6.40-rc1 Mike Frysinger
2011-05-25 19:23 ` Pull request blackfin.git (for-linus branch) Mike Frysinger
2011-04-14 19:27 Mike Frysinger
2011-03-30 5:09 [PATCH 0/3] Blackfin fixes for 2.6.39-rc1 Mike Frysinger
2011-03-30 5:11 ` Pull request blackfin.git (for-linus branch) Mike Frysinger
2011-03-24 5:10 [PATCH 0/4] Blackfin updates for 2.6.39-rc0 (part two) Mike Frysinger
2011-03-24 5:11 ` Pull request blackfin.git (for-linus branch) Mike Frysinger
2011-03-18 18:11 [PATCH 00/32] Blackfin updates for 2.6.39-rc0 Mike Frysinger
2011-03-18 18:12 ` Pull request blackfin.git (for-linus branch) Mike Frysinger
2011-01-10 12:26 [PATCH 00/52] Blackfin updates for 2.6.38 Mike Frysinger
2011-01-11 0:23 ` Pull request blackfin.git (for-linus branch) Mike Frysinger
2010-10-25 9:00 [PATCH 0/5] Blackfin updates for 2.6.37 (part 2) Mike Frysinger
2010-10-26 1:26 ` Pull request blackfin.git (for-linus branch) Mike Frysinger
2010-10-22 22:39 [PATCH 00/47] Blackfin updates for 2.6.37 Mike Frysinger
2010-10-23 3:50 ` Pull request blackfin.git (for-linus branch) Mike Frysinger
2010-08-27 23:08 [PATCH 0/2] Blackfin fixes for 2.6.36-rc2 Mike Frysinger
2010-08-28 20:16 ` Pull request blackfin.git (for-linus branch) Mike Frysinger
2010-08-23 8:40 [PATCH 0/3] Blackfin updates for 2.6.36-rc2 Mike Frysinger
2010-08-23 20:23 ` Pull request blackfin.git (for-linus branch) Mike Frysinger
2010-08-06 16:30 Blackfin updates for 2.6.36-rc0 Mike Frysinger
2010-08-06 20:57 ` Pull request blackfin.git (for-linus branch) Mike Frysinger
2010-05-22 17:10 [PATCH 00/30] Blackfin updates for 2.6.35 Mike Frysinger
2010-05-22 17:13 ` Pull request blackfin.git (for-linus branch) Mike Frysinger
2010-03-09 14:25 [PATCH 00/96] Blackfin updates for 2.6.34 Mike Frysinger
2010-03-09 14:28 ` Pull request blackfin.git (for-linus branch) Mike Frysinger
2009-12-15 17:36 Mike Frysinger
2009-12-15 17:44 ` Mike Frysinger
2009-11-26 21:26 Mike Frysinger
2009-10-09 3:59 Mike Frysinger
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=1299229102-26414-1-git-send-email-vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=uclinux-dist-devel@blackfin.uclinux.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®