From: "Kristian Høgsberg" <krh@redhat.com>
To: Olaf Hering <olh@suse.de>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
linux-kernel@vger.kernel.org,
Jonathan Woithe <jwoithe@physics.adelaide.edu.au>,
akpm@linux-foundation.org, linux1394-devel@lists.sourceforge.net,
torvalds@linux-foundation.org
Subject: Re: [git pull] New firewire stack
Date: Mon, 07 May 2007 20:28:27 -0400 [thread overview]
Message-ID: <463FC42B.7040503@redhat.com> (raw)
In-Reply-To: <20070505211713.GA4016@suse.de>
Olaf Hering wrote:
> On Thu, May 03, Olaf Hering wrote:
>
>> On Thu, May 03, Stefan Richter wrote:
>>
>>> ieee1394-old
>> Noone will seriously ship two firewire stacks, so that cant be the
>> issue (for distributors).
>>
>> Once there is a way to easily switch between kernel releases, I'm ok
>> with whatever module names you pick.
>
> This patch loads fw-sbp2 if sbp2 is still in the config file. So one can
> go back and forth between releases without worry about the root
> filesystem drivers.
That's a good solution, that should work. I've committed it locally, will
push out changes soon.
thanks,
Kristian
next prev parent reply other threads:[~2007-05-08 0:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.197656.1178135675.32383.linux1394-devel@lists.sourceforge.net>
2007-05-03 0:04 ` [git pull] New firewire stack Jonathan Woithe
2007-05-03 8:22 ` Stefan Richter
2007-05-03 11:48 ` Olaf Hering
2007-05-03 13:30 ` Stefan Richter
2007-05-03 16:34 ` Adrian Bunk
2007-05-03 17:33 ` Kristian Høgsberg
2007-05-04 5:54 ` Bill Fink
2007-05-05 21:17 ` Olaf Hering
2007-05-08 0:28 ` Kristian Høgsberg [this message]
2007-05-03 23:07 ` Jonathan Woithe
2007-05-01 20:27 Kristian Høgsberg
2007-05-01 21:34 ` Stefan Richter
2007-05-02 9:00 ` Christoph Hellwig
2007-05-02 12:13 ` Stefan Richter
2007-05-02 20:00 ` Kristian Høgsberg
2007-05-02 12:21 ` Olaf Hering
2007-05-02 12:48 ` Stefan Richter
2007-05-02 13:56 ` Gene Heskett
2007-05-02 18:51 ` Stefan Richter
2007-05-02 15:27 ` Adrian Bunk
2007-05-02 20:03 ` Kristian Høgsberg
2007-05-02 19:53 ` Kristian Høgsberg
2007-05-02 20:03 ` Olaf Hering
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=463FC42B.7040503@redhat.com \
--to=krh@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=jwoithe@physics.adelaide.edu.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=olh@suse.de \
--cc=stefanr@s5r6.in-berlin.de \
--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