archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <>
To: Jon Smirl <>
Cc: lkml <>
Subject: Re: kernel versions on Linus bk tree
Date: Mon, 10 Jan 2005 23:26:51 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>


> I just came across a problem with the way the kernel is being
> versioned. The DRM driver needs an IFDEF for the four level page table
> change depending on kernel version built against. I used this:
> #if LINUX_VERSION_CODE < 0x02060a
> The problem is that 2.6.10 was released on without the four
> level change. But Linus bk which also has version 2.6.10 has the
> change. Is there some way around this problem?
> One solution would be to bump the version in Linus bk to 2.6.11-rc1 on
> the first check in after 2.6.10 is cut. The general case of this would
> be to always bump the Linus bk version number immediately after
> cutting the released version.

2.6.11-rc1 seems wrong, but marking it 2.6.10-bk0 should do the trick.

People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!

  parent reply	other threads:[~2005-01-10 22:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-08 18:23 kernel versions on Linus bk tree Jon Smirl
2005-01-08 18:54 ` Vincent Hanquez
2005-01-08 19:00   ` Vincent Hanquez
2005-01-09  3:44 ` Horst von Brand
2005-01-10 22:26 ` Pavel Machek [this message]
2005-01-10 23:55 ` Ryan Anderson

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).