From: Ben Collins <bcollins@debian.org>
To: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
linux1394-devel@lists.sourceforge.net
Subject: Re: Firewire/SBP2 and the -mm tree (was: Re: 2.6.13-rc1-mm1)
Date: Sat, 2 Jul 2005 09:39:08 -0400 [thread overview]
Message-ID: <20050702133908.GB9300@phunnypharm.org> (raw)
In-Reply-To: <20050702031955.GC28251@ime.usp.br>
Hoping that will occur this weekend.
On Sat, Jul 02, 2005 at 12:19:55AM -0300, Rog?rio Brito wrote:
> Hi, Andrew.
>
> On Friday, 1 of July 2005 13:40, Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc1/2.6.13-rc1-mm1/
>
> Please, correct me if I am wrong, but this doesn't seem to include any
> fixes for the SBP2 problems that I was seeing, right?
>
> I generated a patch from Linus's 2.6.13-rc1 against the trunk of
> linux1394.org's tree containing (as Ben Collins suggested), just the
> differences on sbp2.[ch] and it applied without any problems (no skips, no
> rejects, no nothing) in -rc1-mm1.
>
> I have not tested -rc1-mm1 without the patch, but assuming that all other
> things are equal regarding it, I need this patch for using Firewire on my
> computer.
>
> 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?
>
>
> Thank you very much, Rog?rio.
>
> --
> Rog?rio Brito : rbrito@ime.usp.br : http://www.ime.usp.br/~rbrito
> Homepage of the algorithms package : http://algorithms.berlios.de
> Homepage on freshmeat: http://freshmeat.net/projects/algorithms/
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id\x16492&op=click
> _______________________________________________
> mailing list linux1394-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux1394-devel
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
SwissDisk - http://www.swissdisk.com/
next prev parent reply other threads:[~2005-07-02 13:39 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 ` Firewire/SBP2 and the -mm tree Stefan Richter
2005-07-03 5:33 ` 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 ` Ben Collins [this message]
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=20050702133908.GB9300@phunnypharm.org \
--to=bcollins@debian.org \
--cc=akpm@osdl.org \
--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®