public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 18/21] pci: drop unused Kconfig symbol
Date: Fri, 14 Oct 2011 10:39:55 -0400	[thread overview]
Message-ID: <20111014143954.GA12349@phenom.oracle.com> (raw)
In-Reply-To: <1318602126.6132.99.camel@x61.thuisdomein>

On Fri, Oct 14, 2011 at 04:22:06PM +0200, Paul Bolle wrote:
> On Fri, 2011-10-14 at 16:11 +0200, Paul Bolle wrote:
> > Perhaps this driver is (some part of) xen. That I didn't check. Should I
> > have done that too?
> 
> Obviously, since this symbol in unused now, it's not possible to
> determine what driver is involved. That would be different if this
> Kconfig symbol was actually used previously. But I didn't check - for

Huh? You can look at what it depends and track that down.

> all those symbols involved in this series - why they turned out to be
> unused now. So I can't say whether these symbols should never have been
> in the tree in the first place or whether they were forgotten when
> someone removed their last actual usage.

I am so confused. So lets start with the foremost question I have:

How did you determine that they were unusued?

  reply	other threads:[~2011-10-14 14:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-14 12:30 [PATCH 18/21] pci: drop unused Kconfig symbol Paul Bolle
2011-10-14 13:57 ` Konrad Rzeszutek Wilk
2011-10-14 14:11   ` Paul Bolle
2011-10-14 14:22     ` Paul Bolle
2011-10-14 14:39       ` Konrad Rzeszutek Wilk [this message]
2011-10-14 14:22     ` Konrad Rzeszutek Wilk
2011-10-14 14:30       ` Paul Bolle
2011-10-14 14:42         ` Konrad Rzeszutek Wilk
2011-10-14 14:53           ` 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=20111014143954.GA12349@phenom.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    /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