From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux1394-devel@lists.sourceforge.net
Subject: [git pull] FireWire fixes and documentation update
Date: Thu, 15 Apr 2010 17:59:52 +0200 (CEST) [thread overview]
Message-ID: <tkrat.66ea5df34ac46da2@s5r6.in-berlin.de> (raw)
In-Reply-To: <tkrat.e3130c87f5d2851a@s5r6.in-berlin.de>
Linus, please pull from the for-linus branch at
git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394-2.6.git for-linus
to receive the following IEEE 1394/ FireWire subsystem update.
Thanks.
Clemens Ladisch (3):
firewire: cdev: disallow receive packets without header
firewire: cdev: require quadlet-aligned headers for transmit packets
firewire: cdev: iso packet documentation
Stefan Richter (3):
firewire: cdev: fix information leak
firewire: cdev: comment fixlet
firewire: cdev: change license of exported header files to MIT license
drivers/firewire/core-cdev.c | 23 ++++++-----
include/linux/firewire-cdev.h | 78 +++++++++++++++++++++++++-----------
include/linux/firewire-constants.h | 29 ++++++++++++-
3 files changed, 95 insertions(+), 35 deletions(-)
Since several of these patches were not copied to linux-kernel yet, I
will send the full log and diff in a reply to this message.
--
Stefan Richter
-=====-==-=- -=-- -====
http://arcgraph.de/sr/
next prev parent reply other threads:[~2010-04-15 16:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 18:45 [git pull] FireWire updates post 2.6.33 Stefan Richter
2010-03-26 13:05 ` [git pull] FireWire fixes Stefan Richter
2010-04-15 15:59 ` Stefan Richter [this message]
2010-04-15 16:02 ` [git pull] FireWire fixes and documentation update Stefan Richter
2010-04-15 19:41 ` Daniel K.
2010-04-15 20:30 ` Stefan Richter
2010-04-22 19:45 ` [git pull] FireWire fixes Stefan Richter
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=tkrat.66ea5df34ac46da2@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--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 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.