public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>,
	linux390@de.ibm.com, linux-s390@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] s390: remove HAVE_MARCH_Z9?0_FEATURES
Date: Mon, 17 Feb 2014 09:50:40 +0100	[thread overview]
Message-ID: <1392627040.10966.18.camel@x220> (raw)
In-Reply-To: <20140217082035.GA4651@osiris>

On Mon, 2014-02-17 at 09:20 +0100, Heiko Carstens wrote:
> On Sun, Feb 16, 2014 at 06:15:27PM +0100, Paul Bolle wrote:
> No, I want to keep them, so there is a config symbol for each cpu generation
> and we don't have to add the config symbols again, if we actually use them.

Yes, that's the idea: only add Kconfig symbols that you are actually
going to use.

> It's a question of completeness in this case, not if they are being used.

Completeness of what?

Anyhow, perhaps you can comment this stuff out if you want to have it in
the tree. See, these symbols will pop up each time that people run their
scripts to discover problems in the kconfig space. I suppose this was
probably not the first time these two were reported. And people not
aware of this thread might do that again, and again...

Thanks,


Paul Bolle


  reply	other threads:[~2014-02-17  8:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-16 17:15 [PATCH] s390: remove HAVE_MARCH_Z9?0_FEATURES Paul Bolle
2014-02-17  8:20 ` Heiko Carstens
2014-02-17  8:50   ` Paul Bolle [this message]
2014-02-17  9:10     ` Heiko Carstens
2014-02-17  9:16       ` Paul Bolle

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=1392627040.10966.18.camel@x220 \
    --to=pebolle@tiscali.nl \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux390@de.ibm.com \
    --cc=schwidefsky@de.ibm.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