From: Christoph Hellwig <hch@infradead.org>
To: Marcelo Tosatti <marcelo@conectiva.com.br>, mikael.starvik@axis.com
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.21-pre2
Date: Wed, 18 Dec 2002 23:31:46 +0000 [thread overview]
Message-ID: <20021218233146.A2399@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.50L.0212181721340.18764-100000@freak.distro.conectiva>; from marcelo@conectiva.com.br on Wed, Dec 18, 2002 at 05:22:50PM -0200
> <mikael.starvik@axis.com>:
> o CRIS architecture update for 2.4.21
This seems to include some strange stuff.
It reverts the s/extern __inline__/static __inline__/g changes
in include/asm-cris/ and adds a junk file in
arch/cris/drivers/bluetooth/bt.patch
next prev parent reply other threads:[~2002-12-18 23:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-18 19:22 Linux 2.4.21-pre2 Marcelo Tosatti
2002-12-18 23:31 ` Christoph Hellwig [this message]
2002-12-19 1:16 ` Alan Cox
2002-12-18 23:33 ` Eyal Lebedinsky
2002-12-18 23:49 ` Linux 2.4.21-pre2 - unresolved Eyal Lebedinsky
2002-12-20 14:48 ` Linux 2.4.21-pre2 Adrian Bunk
2002-12-20 14:57 ` Christoph Hellwig
2002-12-20 15:50 ` Ben Collins
-- strict thread matches above, loose matches on Subject: below --
2002-12-19 6:49 Mikael Starvik
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=20021218233146.A2399@infradead.org \
--to=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=mikael.starvik@axis.com \
/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