All of lore.kernel.org
 help / color / mirror / Atom feed
From: Elias Oltmanns <eo@nebensachen.de>
To: "Loïc Grenié" <loic.grenie@gmail.com>, "Ingo Molnar" <mingo@elte.hu>
Cc: "Greg KH" <gregkh@suse.de>,
	linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: Linux 2.6.27.6
Date: Sat, 15 Nov 2008 17:12:52 +0100	[thread overview]
Message-ID: <873ahtotmj.fsf@denkblock.local> (raw)
In-Reply-To: <9b06e8d20811150701q6e38148k18df241343262713@mail.gmail.com> ("Loïc Grenié"'s message of "Sat, 15 Nov 2008 16:01:32 +0100")

"Loïc Grenié" <loic.grenie@gmail.com> wrote:
> 2008/11/15 Elias Oltmanns <eo@nebensachen.de>:
>> "Loïc Grenié" <loic.grenie@gmail.com> wrote:
>
>>>     No big deal, but commit 093327cb references
>>>   X86_CHECK_BIOS_CORRUPTION that is not available anywhere.
>>
>> You are talking about commit 71556e92, I suppose. Since the change log
>> entry has been written for the original commit 5649b7c3 in Linus' tree,
>> it refers to a feature that is available there
>> (X86_CHECK_BIOS_CORRUPTION) but has only been merged into mainline after
>> the release of 2.6.27.
>
>     No, I really mean 093327cb because it modifies arch/x86/Kconfig and in the
>   help for X86_RESERVE_LOW_64K it references
>   X86_CHECK_BIOS_CORRUPTION that, as you say, exists only in 2.6.28-rc?

Right, I see. Perhaps Ingo wants to do something about it?

Regards,

Elias

  reply	other threads:[~2008-11-15 16:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-13 18:53 Linux 2.6.27.6 Greg KH
2008-11-13 18:56 ` Greg KH
2008-11-14  5:14 ` CaT
2008-11-14 17:34   ` [stable] " Greg KH
2008-11-15 10:38 ` Loïc Grenié
2008-11-15 12:12   ` Elias Oltmanns
2008-11-15 15:01     ` Loïc Grenié
2008-11-15 16:12       ` Elias Oltmanns [this message]
2008-11-18 17:20 ` Eric Sandall
2008-11-18 23:56   ` Grant Coady
2008-11-19  0:08     ` Eric Sandall
2008-11-19  6:15   ` Greg KH
2008-11-22  2:24     ` Eric Sandall

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=873ahtotmj.fsf@denkblock.local \
    --to=eo@nebensachen.de \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loic.grenie@gmail.com \
    --cc=mingo@elte.hu \
    --cc=stable@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.