From: Mikael Starvik <mikael.starvik@axis.com>
To: "'Greg KH'" <greg@kroah.com>,
"'Mikael Starvik'" <mikael.starvik@axis.com>
Cc: "'Linux Kernel Mailing List'" <linux-kernel@vger.kernel.org>
Subject: RE: CRIS architecture update
Date: Thu, 10 Jul 2003 22:24:56 +0200 [thread overview]
Message-ID: <3C6BEE8B5E1BAC42905A93F13004E8AB03277AA5@mailse01.axis.se> (raw)
>Speaking of older kernels, any chances for a 2.5 update?
Yes. I have sent patches to Linus several times, the latest one today.
So far he has been dropping my patches on the floor.
So far our 2.5 tree doesn't have a USB driver because I
would like to wait until the USB framework is less volatile.
In my mind we will port the USB driver somewhere around
2.6.0.
/Mikael
-----Original Message-----
From: Greg KH [mailto:greg@kroah.com]
Sent: Thursday, July 10, 2003 7:15 PM
To: Mikael Starvik
Cc: 'Linux Kernel Mailing List'
Subject: Re: CRIS architecture update
On Thu, Jul 10, 2003 at 10:13:41AM -0700, Greg KH wrote:
> On Thu, Jul 10, 2003 at 07:24:58AM +0200, Mikael Starvik wrote:
> > Ok, do you have any other suggestion on how to make the driver
> > compilable for both >= 2.4.20 and < 2.4.20?
>
> As the driver is _in_ the kernel tree, why does it need to be compilable
> for older kernels? :)
Speaking of older kernels, any chances for a 2.5 update? I know the
CRIS USB host controller driver has fallen pretty out of date with the
rest of the USB core, and would hope to see that sync up sometime.
thanks,
greg k-h
next reply other threads:[~2003-07-10 20:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-10 20:24 Mikael Starvik [this message]
2003-07-10 20:48 ` CRIS architecture update Greg KH
-- strict thread matches above, loose matches on Subject: below --
2003-07-10 20:26 Mikael Starvik
[not found] <3C6BEE8B5E1BAC42905A93F13004E8AB034C5655@mailse01.axis.se>
2003-07-10 5:24 ` Mikael Starvik
2003-07-10 17:13 ` Greg KH
2003-07-10 17:14 ` Greg KH
[not found] <200307091905.h69J5srp005054@hera.kernel.org>
2003-07-09 20:15 ` Greg KH
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=3C6BEE8B5E1BAC42905A93F13004E8AB03277AA5@mailse01.axis.se \
--to=mikael.starvik@axis.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).