From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: linux-kernel@vger.kernel.org, linux1394-devel@lists.sourceforge.net
Cc: "Rogério Brito" <rbrito@ime.usp.br>, "Andrew Morton" <akpm@osdl.org>
Subject: Re: Firewire/SBP2 and the -mm tree
Date: Sat, 02 Jul 2005 11:56:30 +0200 [thread overview]
Message-ID: <42C664CE.9020009@s5r6.in-berlin.de> (raw)
In-Reply-To: <20050702031955.GC28251@ime.usp.br>
Rogério Brito wrote:
> Is there any estimated possibility of including an update from the
> linux1394 team in future versions of -mm or, even better, pushing them to
> Linus's tree?
That is what usually happens. But the sbp2 related diffs between 2.6.13
and linux1394 are not an update by linux1394 but rather a rewrite by the
scsi folk. Unfortunately, that rewrite was not tested by the linux1394
team. (And was therefore not checked in at svn.linux1394.org. Lack of
manpower was one factor.) So, applying the sbp2 portion of your diff is
a back-out, not an update.
I have a question: Do you need _both_ the sbp2 back-out and ieee1394's
disable_irm parameter, or only one of them?
--
Stefan Richter
-=====-=-=-= -=== ---=-
http://arcgraph.de/sr/
next prev parent reply other threads:[~2005-07-02 9:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-01 11:40 2.6.13-rc1-mm1 Andrew Morton
2005-07-01 12:33 ` 2.6.13-rc1-mm1 Daniel Andersen
2005-07-01 22:05 ` 2.6.13-rc1-mm1 Rafael J. Wysocki
2005-07-02 3:19 ` Firewire/SBP2 and the -mm tree (was: Re: 2.6.13-rc1-mm1) Rogério Brito
2005-07-02 4:34 ` Rogério Brito
2005-07-02 9:56 ` Stefan Richter [this message]
2005-07-03 5:33 ` Firewire/SBP2 and the -mm tree Rogério Brito
2005-07-03 18:04 ` Rogério Brito
2005-07-03 20:03 ` Stefan Richter
2005-07-04 20:05 ` Rogério Brito
2005-07-02 13:39 ` Firewire/SBP2 and the -mm tree (was: Re: 2.6.13-rc1-mm1) Ben Collins
2005-07-04 20:27 ` 2.6.13-rc1-mm1 Alexey Dobriyan
2005-07-02 0:22 ` [PATCH] sched: consider migration thread with smp nice Con Kolivas
2005-07-02 2:43 ` 2.6.13-rc1-mm1 Dominik Karall
2005-07-02 2:55 ` 2.6.13-rc1-mm1 randy_dunlap
2005-07-02 5:39 ` 2.6.13-rc1-mm1 Grant Coady
2005-07-02 9:16 ` 2.6.13-rc1-mm1: git-mtd.patch breaks i386 compile Adrian Bunk
2005-07-02 9:37 ` Thomas Gleixner
2005-07-04 23:04 ` Thomas Gleixner
2005-07-04 12:36 ` 2.6.13-rc1-mm1 Joseph Fannin
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=42C664CE.9020009@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=rbrito@ime.usp.br \
/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®