From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, devel@linuxdriverproject.org
Subject: [GIT PATCH] staging driver fixes for 3.4-rc5
Date: Sun, 29 Apr 2012 09:15:30 -0700 [thread overview]
Message-ID: <20120429161530.GA16514@kroah.com> (raw)
The following changes since commit 66f75a5d028beaf67c931435fdc3e7823125730c:
Linux 3.4-rc4 (2012-04-21 14:47:52 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/ tags/staging-3.4-rc4
for you to fetch changes up to 89f21cc050d5eed8eeffee5b46297fb7a74ef9dd:
staging: ozwpan: Fix bug where kfree is called twice. (2012-04-26 12:40:53 -0700)
----------------------------------------------------------------
Staging tree fixes for 3.4-rc4
Here are some tiny drivers/staging/ bugfixes. Some build fixes that
were recently reported, as well as one kfree bug that is hitting a
number of users.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----------------------------------------------------------------
Imre Kaloz (1):
staging: octeon-ethernet: fix build errors by including interrupt.h
Omar Ramirez Luna (1):
staging: tidspbridge: remove usage of OMAP2_L4_IO_ADDRESS
Rupesh Gujare (1):
staging: ozwpan: Fix bug where kfree is called twice.
Seth Jennings (1):
staging: zcache: fix Kconfig crypto dependency
drivers/staging/octeon/ethernet-rx.c | 1 +
drivers/staging/octeon/ethernet-tx.c | 1 +
drivers/staging/octeon/ethernet.c | 1 +
drivers/staging/ozwpan/ozpd.c | 2 --
drivers/staging/tidspbridge/core/tiomap3430.c | 20 ++++++++++++--------
drivers/staging/tidspbridge/core/wdt.c | 8 +++++++-
drivers/staging/zcache/Kconfig | 2 +-
7 files changed, 23 insertions(+), 12 deletions(-)
reply other threads:[~2012-04-29 16:15 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=20120429161530.GA16514@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=devel@linuxdriverproject.org \
--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
all inboxes | Powered by JetHome®