public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anders Karlsson <anders@trudheim.com>
To: Mike Fedyk <mfedyk@matchmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: BK 2.6.1 Kernel
Date: Tue, 20 Jan 2004 21:46:42 +0000	[thread overview]
Message-ID: <1074635202.9075.5.camel@tor.trudheim.com> (raw)
In-Reply-To: <20040120181251.GC23765@srv-lnx2600.matchmail.com>

[-- Attachment #1: Type: text/plain, Size: 849 bytes --]

On Tue, 2004-01-20 at 18:12, Mike Fedyk wrote:

> Is that the taged 2.6.1 release, or does it have patches integrated after
> that tag?

That is the tagged 2.6.1 release. I looked at what change set
(1.1474.2.29) the Makefile was in when the change from 2.6.1-rc3 to
2.6.1 took place, and exported that. I could take a kernel.org tarball,
but the result will probably be exactly the same.

2.6.1 works.

2.6.1 + bk changes from
http://linux-acpi.bkbits.net:8080/linux-acpi-test-2.6.1 and
http://linux.bkbits.net:8080/linux-2.5 up until Monday 19th at about
12:00 GMT does not.

Boot params, configuration, everything as similar as can be.

> Try with a tarbal from kernel.org instead.

Will do that in the morning. Almost bed-time here. :)

Regards,

-- 
Anders Karlsson <anders@trudheim.com>
Trudheim Technology Limited

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2004-01-20 21:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-19 15:41 BK 2.6.1 Kernel Anders Karlsson
2004-01-19 15:58 ` Mike Fedyk
2004-01-20  9:46   ` Anders Karlsson
2004-01-20 14:46   ` Anders Karlsson
2004-01-20 18:12     ` Mike Fedyk
2004-01-20 21:46       ` Anders Karlsson [this message]

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=1074635202.9075.5.camel@tor.trudheim.com \
    --to=anders@trudheim.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfedyk@matchmail.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