mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Yinghai Lu" <yhlu.kernel@gmail.com>
Cc: "Grant Grundler" <grundler@parisc-linux.org>,
	"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:32:41 -0700	[thread overview]
Message-ID: <200805230832.42047.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <86802c440805222338w3c8e946eree2d090ce12609e@mail.gmail.com>

On Thursday, May 22, 2008 11:38 pm Yinghai Lu wrote:
> > Please call this "pci_early_dump" (I prefer with underscores but don't
> > care). Don't want it confused with kernel dumps (LKCD) or any other
> > general debugging tools.
>
> so you want pci_early_dump instead of pci=earlydump?
> or pci=early_dump?

Or early_config_dump, I don't have a strong preference (but Grant's right that 
a pci_ prefix should be on there somewhere, either pci= or pci_).

Can you send me a replacement for the patch that added it once you come up 
with something?

Thanks,
Jesse

  reply	other threads:[~2008-05-23 15:33 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 [this message]
2008-05-25 22:37       ` Grant Grundler
2008-05-23 15:30     ` Jesse Barnes
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=200805230832.42047.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