From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: linux-next: left over things in linux-next after 2.6.28-c1
Date: Sun, 26 Oct 2008 08:40:33 +0100 [thread overview]
Message-ID: <49041EF1.8070508@s5r6.in-berlin.de> (raw)
In-Reply-To: <20081026005009.50dbbb33.sfr@canb.auug.org.au>
Stephen Rothwell wrote:
> The following is an approximate list of commits left in linux-next
> relative to 2.6.28-rc1.
...
> ieee1394
>
> David Moore (1):
> firewire: Include iso timestamp in headers when header_size > 4
>
> Jay Fenlason (2):
> firewire: add a client_list_lock
> firewire: Survive more than 256 bus resets
>
> Stefan Richter (2):
> firewire: fw-sbp2: extend failure check after SCSI probe
> firewire: convert client_list_lock to mutex
1x new fix for a pull request soon
1x obsoleted by belated info from a problem reporter
3x things which turned out unfit for -next pre 2.6.28-rc1 but I was too
lazy to temporarily revert in my for-next branch
--
Stefan Richter
-=====-==--- =-=- ==-=-
http://arcgraph.de/sr/
next prev parent reply other threads:[~2008-10-26 7:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-25 13:50 linux-next: left over things in linux-next after 2.6.28-c1 Stephen Rothwell
2008-10-25 13:58 ` Al Viro
2008-10-25 14:37 ` Sam Ravnborg
2008-10-25 21:16 ` Greg KH
2008-10-25 21:52 ` Sam Ravnborg
2008-10-25 22:10 ` Greg KH
2008-10-28 5:34 ` Ananth N Mavinakayanahalli
2008-10-29 23:53 ` Greg KH
2008-10-25 21:20 ` Greg KH
2008-10-25 23:48 ` Randy Dunlap
2008-10-26 0:07 ` Randy Dunlap
2008-10-26 7:40 ` Stefan Richter [this message]
2008-10-26 8:17 ` Christoph Hellwig
2008-10-26 8:34 ` Stephen Rothwell
2008-10-26 8:39 ` Christoph Hellwig
2008-10-27 7:44 ` Lachlan McIlroy
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=49041EF1.8070508@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.