From: "Mikael Starvik" <mikael.starvik@axis.com>
To: "'Sam Ravnborg'" <sam@ravnborg.org>,
"Björn Wesén" <bjorn.wesen@axis.com>
Cc: "'Dan Kegel'" <dank@kegel.com>,
"'Mikael Starvik'" <mikael.starvik@axis.com>,
<linux-kernel@vger.kernel.org>
Subject: RE: Delete cris architecture?
Date: Tue, 1 Jun 2004 07:17:33 +0200 [thread overview]
Message-ID: <BFECAF9E178F144FAEF2BF4CE739C66818F48E@exmail1.se.axis.com> (raw)
In-Reply-To: <BFECAF9E178F144FAEF2BF4CE739C668CD62C1@exmail1.se.axis.com>
Hi!
The CRIS architecture is very much alive and locally we are running 2.6.6.
It is true that I haven't submitted any patches since 2.5.74 or
something like that. It is my intention to send in a patch asap,
hopefully this week.
I will submit 2.6 patches more often in the future. Later this year
we will also add support for a new CRIS subarchitecture.
/Mikael (CRIS maintainer)
-----Original Message-----
From: linux-kernel-owner@vger.kernel.org
[mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Sam Ravnborg
Sent: Monday, May 31, 2004 8:42 PM
To: Björn Wesén
Cc: Dan Kegel; Mikael Starvik; linux-kernel@vger.kernel.org
Subject: Re: Delete cris architecture?
On Mon, May 31, 2004 at 06:14:02PM +0200, Bjorn Wesen wrote:
> The CRIS architecture is stable and supported by Axis Communications
> officially in 2.4, but the 2.6 port is work-in-progress, thus you could
> expect problems building it from the vanilla kernel source. It works
> in-house on 2.6, but perhaps all patches have not trickled out to the
> official kernel yet (although they should have I think, so it's good that
> you mention stuff like this).
When grepping the source and even doing cross architecture changes it is
nice to have a ratehr up-to-date version in the main stream kernel.
It would be nice if Axis could at least drop an update of the tree for
each kernel release (provided there are any changes).
This would allow all of us to get a better overview, and in some cases
we may even introduce new stuff / fix errors.
So please start to feed Andrew (or Linus) regularly with updates.
Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
next parent reply other threads:[~2004-06-01 5:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BFECAF9E178F144FAEF2BF4CE739C668CD62C1@exmail1.se.axis.com>
2004-06-01 5:17 ` Mikael Starvik [this message]
2004-06-01 4:51 ` Dan Kegel
2004-05-31 13:46 Dan Kegel
2004-05-31 14:29 ` Ben Collins
2004-05-31 16:14 ` Bjorn Wesen
2004-05-31 18:42 ` Sam Ravnborg
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=BFECAF9E178F144FAEF2BF4CE739C66818F48E@exmail1.se.axis.com \
--to=mikael.starvik@axis.com \
--cc=bjorn.wesen@axis.com \
--cc=dank@kegel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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®