From: Greg KH <greg@kroah.com>
To: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PATCH] STAGING patches for 2.6.30-rc4 tree
Date: Fri, 8 May 2009 20:24:43 -0700 [thread overview]
Message-ID: <20090509032443.GC9000@kroah.com> (raw)
Here are some patches for your 2.6.30-rc4 git tree.
It contains:
- a new device id.
- documentation update to keep someone from getting unwanted
emails.
- 2 bugfixes
All of these are contained within the drivers/staging tree, and have
been in the linux-next and -mm trees for a while now.
Please pull from:
master.kernel.org:/pub/scm/linux/kernel/git/gregkh/staging-2.6.git/
thanks,
greg k-h
--------------
drivers/staging/comedi/TODO | 1 -
drivers/staging/rt2870/rt2870.h | 1 +
drivers/staging/rtl8187se/r8180.h | 2 +-
drivers/staging/rtl8187se/r8180_core.c | 46 +++++--------------------------
drivers/staging/winbond/wbusb.c | 9 +++++-
5 files changed, 17 insertions(+), 42 deletions(-)
---------------
Dave Hayes (1):
Staging: rt2870: new device id
Greg Kroah-Hartman (1):
Staging: comedi: David doesn't want to get comedi patches
Larry Finger (1):
Staging: rtl8187se: Fix compilation warnings and procfs directory leak
Pekka Enberg (1):
Staging: w35und: unregister device from the ieee80211 stack upon ->disconnect()
next reply other threads:[~2009-05-09 3:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-09 3:24 Greg KH [this message]
2009-05-09 3:26 ` [PATCH 1/4] Staging: w35und: unregister device from the ieee80211 stack upon ->disconnect() Greg Kroah-Hartman
2009-05-09 3:26 ` [PATCH 2/4] Staging: rt2870: new device id Greg Kroah-Hartman
2009-05-09 3:26 ` [PATCH 3/4] Staging: rtl8187se: Fix compilation warnings and procfs directory leak Greg Kroah-Hartman
2009-05-09 3:26 ` [PATCH 4/4] Staging: comedi: David doesn't want to get comedi patches Greg Kroah-Hartman
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=20090509032443.GC9000@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.