linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Karsten Keil <kkeil@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: liste@jordet.nu, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, linus@osdl.org
Subject: Re: 2.6.3-rc1-mm1
Date: Tue, 10 Feb 2004 03:25:10 +0100	[thread overview]
Message-ID: <20040210022510.GA17364@pingi3.kke.suse.de> (raw)
In-Reply-To: <20040209112207.4e7d97c9.akpm@osdl.org>

On Mon, Feb 09, 2004 at 11:22:07AM -0800, Andrew Morton wrote:
> Karsten Keil <kkeil@suse.de> wrote:
> >
> > I have also BitKeeper running here with a clone of the linux-2.5
> > tree,
> 
> Is this the master tree, or is this a copy of what is in i4l CVS?

It is a bk clone http://linux.bkbits.net:8080/linux-2.5

And I  imported the i4l-2.6.3-rc1-bk2 patch

> 
> Either way, let's find a way in which I can obtain the latest version and
> also be kept up to date with any fixes.  Thanks.

Here are the latest versions, since they are so big only as reference:
Linus tree:
ftp://ftp.isdn4linux.de/pub/isdn4linux/kernel/v2.6/i4l-2.6.3-rc1-bk2.gz

Andrew tree:
ftp://ftp.isdn4linux.de/pub/isdn4linux/kernel/v2.6/i4l-2.6.3-rc1-mm1.gz

The result of both patches are the same source, but in Andrews tree
some smaller fixes were already included, to avoid rejects I
created patches for both trees.

ChangeLog:

- new port of 2.4 I4L core to 2.6
- new port of 2.4 I$L HiSax to 2.6
- fixes for I4L CAPI subsystem to make it stable in 2.6
- fix parameter handling of AVM ISA cards (calle)
- cleanup ISDN config variables

These patches are in sync with I4L cvs (kernel 2.6 branch).

-- 
Karsten Keil
SuSE Labs
ISDN development
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2004-02-10  2:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-09  9:40 2.6.3-rc1-mm1 Andrew Morton
2004-02-09  9:50 ` 2.6.3-rc1-mm1 Stian Jordet
2004-02-09 10:24   ` 2.6.3-rc1-mm1 Andrew Morton
2004-02-09 10:29     ` 2.6.3-rc1-mm1 Stian Jordet
2004-02-09 11:56     ` 2.6.3-rc1-mm1 Karsten Keil
2004-02-09 19:22       ` 2.6.3-rc1-mm1 Andrew Morton
2004-02-10  2:25         ` Karsten Keil [this message]
2004-02-09 14:18 ` 2.6.3-rc1-mm1 Philippe Gramoullé
2004-02-09 23:58   ` 2.6.3-rc1-mm1 Andrew Morton
2004-02-10  0:05     ` 2.6.3-rc1-mm1 Philippe Gramoullé
2004-02-11 23:53     ` 2.6.3-rc1-mm1 Philippe Gramoullé
2004-02-09 16:44 ` 2.6.3-rc1-mm1 Dominik Kubla
2004-02-09 17:42   ` 2.6.3-rc1-mm1 Andrew Morton
2004-02-09 16:54 ` 2.6.3-rc1-mm1 James Morris
2004-02-10 19:45 ` 2.6.3-rc1-mm1 Brian Jackson
2004-02-10 21:05   ` 2.6.3-rc1-mm1 Andrew Morton
2004-02-10 23:51 ` 2.6.3-rc1-mm1 (SELinux + ext3 + nfsd oops) Chris PeBenito
2004-02-11  2:29   ` James Morris
2004-02-11  3:45     ` Chris PeBenito
2004-02-11  5:03       ` James Morris
2004-02-11 17:08 ` 2.6.3-rc1-mm1 Mark Haverkamp
2004-02-14  2:04 ` VM Acct patch (was Re: 2.6.3-rc1-mm1) Eugene Teo

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=20040210022510.GA17364@pingi3.kke.suse.de \
    --to=kkeil@suse.de \
    --cc=akpm@osdl.org \
    --cc=linus@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=liste@jordet.nu \
    /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