mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux1394-devel@lists.sourceforge.net
Subject: Re: [GIT PULL] ieee1394 fixes post 2.6.22-rc2
Date: Wed, 23 May 2007 13:15:20 +0200	[thread overview]
Message-ID: <46542248.3090507@s5r6.in-berlin.de> (raw)
In-Reply-To: <tkrat.5299b7dd67007e8c@s5r6.in-berlin.de>

I wrote on 2007-05-19:
> 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 subsystem updates:
> 
>   - fix regression in 2.6.22-rc1:
>     raw1394 asynchronous transmit was broken
> 
>   - fix old bug in raw1394:
>     32bit compat code for 64bit kernels was broken and incomplete
> 
>   - fix old eth1394 bug:
>     packets were frequently dropped in transmit path
>     (This fixes only the most common type of failure, tlabel exhaustion.)
> 
>   - trivial sbp2 fix

Linus,

if you didn't pull already, please don't.  Rather wait for my next batch
of -rc fixes.  At the moment it looks as if I should postpone raw1394's
32bit compat fixes (or call them feature addition) until after the
release of 2.6.22 to ensure we get them right.

Thanks,
-- 
Stefan Richter
-=====-=-=== -=-= =-===
http://arcgraph.de/sr/

  parent reply	other threads:[~2007-05-23 11:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-29 23:03 [GIT PULL] ieee1394 updates post 2.6.21 Stefan Richter
2007-05-19 11:39 ` [GIT PULL] ieee1394 fixes post 2.6.22-rc2 Stefan Richter
2007-05-19 11:40   ` Stefan Richter
2007-05-23 11:15   ` Stefan Richter [this message]
2007-05-27 21:45     ` [GIT PULL] ieee1394 fixes post 2.6.22-rc3 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=46542248.3090507@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --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 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®