From: Joe Perches <joe@perches.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, Yinghai Lu <yhlu.kernel@gmail.com>,
Len Brown <lenb@kernel.org>
Subject: Re: [PATCH v2 3/9] vsprintf: add %pR decoding and %pr for raw struct resource
Date: Tue, 13 Oct 2009 13:32:00 -0700 [thread overview]
Message-ID: <1255465920.18975.72.camel@Joe-Laptop.home> (raw)
In-Reply-To: <200910131407.08290.bjorn.helgaas@hp.com>
On Tue, 2009-10-13 at 14:07 -0600, Bjorn Helgaas wrote:
> On Tuesday 13 October 2009 01:40:08 pm Joe Perches wrote:
> > On Tue, 2009-10-13 at 13:22 -0600, Bjorn Helgaas wrote:
> > > This adds support for printing struct resource type and flag information.
> > > For example, "%pR" looks like "[mem 0xf5df0000-0xf5df3fff 64bit pref]",
> > > and "%pr" looks like "[mem 0xff5e2000-0xff5e2007 flags 0x201]".
> > Isn't it better to avoid using multiple characters
> > for a single type?
> I followed the example of F/f, S/s, M/m, etc. I could
> easily go back to %pR/%pRf or something, but I don't know
> if it's worth the trouble.
I'd prefer %pR and %pRr for raw, but maybe that's just me.
cheers, Joe
next prev parent reply other threads:[~2009-10-13 20:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 19:21 [PATCH v2 0/9] PCI, PNP: print resources consistently Bjorn Helgaas
2009-10-13 19:22 ` [PATCH v2 1/9] vsprintf: fix io/mem resource width Bjorn Helgaas
2009-10-13 19:22 ` [PATCH v2 2/9] vsprintf: add %pR support for IRQ and DMA resources Bjorn Helgaas
2009-10-13 19:22 ` [PATCH v2 3/9] vsprintf: add %pR decoding and %pr for raw struct resource Bjorn Helgaas
2009-10-13 19:40 ` Joe Perches
2009-10-13 20:07 ` Bjorn Helgaas
2009-10-13 20:32 ` Joe Perches [this message]
2009-10-13 19:22 ` [PATCH v2 4/9] PCI: set IORESOURCE_MEM_64 before printing resource Bjorn Helgaas
2009-10-13 19:22 ` [PATCH v2 5/9] PCI: trivial bridge resource factorization Bjorn Helgaas
2009-10-13 19:22 ` [PATCH v2 6/9] PCI: print resources consistently with %pR Bjorn Helgaas
2009-10-13 19:22 ` [PATCH v2 7/9] x86/PCI: " Bjorn Helgaas
2009-10-13 19:22 ` [PATCH v2 8/9] ia64/PCI: " Bjorn Helgaas
2009-10-13 19:22 ` [PATCH v2 9/9] PNP: " Bjorn Helgaas
2009-10-14 6:47 ` [PATCH v2 0/9] PCI, PNP: print resources consistently Yinghai Lu
2009-10-14 15:52 ` Bjorn Helgaas
2009-10-22 22:53 ` Bjorn Helgaas
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=1255465920.18975.72.camel@Joe-Laptop.home \
--to=joe@perches.com \
--cc=bjorn.helgaas@hp.com \
--cc=jbarnes@virtuousgeek.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--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