From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: linux-kernel@vger.kernel.org
Cc: linux1394-devel@lists.sourceforge.net
Subject: What's in linux1394-2.6.git
Date: Wed, 26 Sep 2007 21:42:30 +0200 (CEST) [thread overview]
Message-ID: <tkrat.37c4d4be47f119fa@s5r6.in-berlin.de> (raw)
I heard that project tree maintainers are encouraged to post merge plans
in time, so I'm going to do so now too. Although this time there isn't
much in store for drivers/{ieee1394,firewire} for the merge window
because we all got sidetracked lately... It's basically bugfixes which
I felt were too late for 2.6.23.
To be merged:
Jean Delvare (1):
ieee1394: pcilynx: I2C cleanups
Satyam Sharma (1):
ieee1394: Fix kthread stopping in nodemgr_host_thread
Stefan Richter (18):
ieee1394: eth1394: superfluous local variable
ieee1394: eth1394: fix lock imbalance
ieee1394: pcilynx: superfluous local variables
ieee1394: sbp2: fix unsafe iteration over list of devices
firewire: optimize fw_core_add_address_handler
firewire: fw-core: local variable shadows a global one
firewire: fw-sbp2: always enable IRQs before calling command ORB callback
firewire: fw-sbp2: add support for multiple logical units per target
firewire: fw-sbp2: expose module parameter for workarounds
firewire: fw-sbp2: use an own workqueue (fix system responsiveness)
firewire: fw-ohci: enforce read order for selfID generation
firewire: fw-ohci: fix includes
firewire: fw-ohci: reorder includes
firewire: fw-ohci: log posted write errors
firewire: fw-ohci: missing dma_unmap_single
firewire: fw-ohci: check for misconfigured bus (phyID == 63)
ieee1394: nodemgr: fix leak of struct csr1212_keyval
ieee1394: csr1212: proper refcounting
On hold for debugging:
Kristian Høgsberg (1):
firewire: Fix pci resume to not pass in a __be32 config rom.
--
Stefan Richter
-=====-=-=== =--= ==-=-
http://arcgraph.de/sr/
reply other threads:[~2007-09-26 19:43 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=tkrat.37c4d4be47f119fa@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
/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®