mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@novell.com>
To: <dsd@laptop.org>
Cc: <linux-kernel@vger.kernel.org>, <hpa@zytor.com>
Subject: your patch "x86, olpc: Rework BIOS signature check"
Date: Fri, 26 Nov 2010 13:18:18 +0000	[thread overview]
Message-ID: <4CEFC1AA0200007800024734@vpn.id2.novell.com> (raw)

... adds a select of OLPC_OPENFIRMWARE to the OLPC option,
which contradicts OLPC_OPENFIRMWARE itself depending on
!X86_64 && !X86_PAE. Are the latter dependencies not necessary
anymore (the X86_64 one wasn't very meaningful anyway, since
these options all sit inside a "if X86_32"), or should the select be
conditional?

Also, how meaningful is having OLPC_OPENFIRMWARE on but OLPC
off (i.e. can OLPC_OPENFIRMWARE perhaps go away altogether)?

Thanks, Jan


             reply	other threads:[~2010-11-26 13:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-26 13:18 Jan Beulich [this message]
2010-11-26 20:34 ` Daniel Drake

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=4CEFC1AA0200007800024734@vpn.id2.novell.com \
    --to=jbeulich@novell.com \
    --cc=dsd@laptop.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®