mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: Yinghai Lu <yhlu.kernel@gmail.com>, Ingo Molnar <mingo@elte.hu>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-pci@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: early dump pci conf space v2
Date: Fri, 23 May 2008 08:30:28 -0700	[thread overview]
Message-ID: <200805230830.28699.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <20080523053822.GA28835@colo.lackof.org>

On Thursday, May 22, 2008 10:38 pm Grant Grundler wrote:
> On Thu, May 22, 2008 at 02:35:11PM -0700, Yinghai Lu wrote:
> > so we can printout pci config before kernel touch it
> >
> > Signed-off-by: Yinghai Lu <yhlu.kernel@gmail.com>
>
> Yinghai,
> No offense, but my first thought was this is debug code that should be
> maintained outside the kernel.org tree. It will rarely get used.
> Just want people to think about this before saying "great, add it!"
>
> (And this isn't a stab at Jesse since I think he's doing a better
> job than I could. I saw his previous reply to this mail.)
>
> Having debugged lots of PCI resource and config issues, I understand
> why this is useful and do NOT object to it being included in the tree.

Yeah I thought about this too, but:
  1) it's definitely useful for debugging PCI issues, and much easier for 
everyone if it's in-tree
  2) it only bloats x86 kernels ;)

Documentation is definitely needed though, thanks for catching that.

Thanks,
Jesse

  parent reply	other threads:[~2008-05-23 15:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-21  7:12 [PATCH] x86: early dump pci conf space Yinghai Lu
2008-05-22 18:42 ` Jesse Barnes
2008-05-22 21:35 ` [PATCH] x86: early dump pci conf space v2 Yinghai Lu
2008-05-22 23:15   ` Jesse Barnes
2008-05-23  5:38   ` Grant Grundler
2008-05-23  6:38     ` Yinghai Lu
2008-05-23 15:32       ` Jesse Barnes
2008-05-25 22:37       ` Grant Grundler
2008-05-23 15:30     ` Jesse Barnes [this message]
2008-05-23 19:48   ` [PATCH] x86: early dump pci conf space v3 Yinghai Lu
2008-05-25 22:45     ` Grant Grundler
2008-05-22 21:35 ` [PATCH] x86: write_pci_config_byte fix offset Yinghai Lu
2008-05-22 23:14   ` Jesse Barnes

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=200805230830.28699.jbarnes@virtuousgeek.org \
    --to=jbarnes@virtuousgeek.org \
    --cc=akpm@linux-foundation.org \
    --cc=grundler@parisc-linux.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=yhlu.kernel@gmail.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

Powered by JetHome