From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Vincent Legoll" <vincent.legoll@gmail.com>
Cc: "Bjorn Helgaas" <bjorn.helgaas@hp.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI probing debug message uniformization
Date: Fri, 10 Oct 2008 09:07:35 -0700 [thread overview]
Message-ID: <200810100907.35798.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <4727185d0810031550l32592f7ep2d1d37f93be12874@mail.gmail.com>
On Friday, October 3, 2008 3:50 pm Vincent Legoll wrote:
> On Fri, Oct 3, 2008 at 8:57 PM, Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
> > It'll be easier for Jesse if you include the proper changelog again
> > with just a 1-2 line sample of the changed messages. BTW, the "--"
> > before your sig confused my mailer into not quoting the patch itself,
> > hence the screwed up formatting below.
>
> The "-- " line is the start-of-.sig marker have I been taught in my
> school days, I think they then spoke about netiquette...
>
> > dev_info() is exactly equivalent to dev_printk(KERN_INFO). I usually
> > use dev_info(), though I'm a bit ambivalent because it's nice to be
> > able to grep for "printk".
>
> I left dev_printk(KERN_INFO, ...) for grepability
>
> > Anyway, maybe you can correct the grammar
> > of "enabled forcedly" to something like "you can enable with ..." when
> > you re-post with the changelog.
>
> I've used "You can enable it back with", hoping the gramar is right
>
> > (Note that dev_dbg() is NOT exactly equivalent to dev_printk(KERN_DEBUG),
> > so you can't change all of them. dev_printk(KERN_DEBUG) is always
> > compiled in, while dev_dbg() is only compiled in when "DEBUG" is
> > defined.)
>
> Thanks for the hint, for I may have jumped the gun on those "other"
> cleanups ;-)
>
> So here is the new version cut'n'pasted from git-format-patch
Can you respin against linux-next and send me a fresh copy? This one seems to
have been corrupted somehow (sorry for the slow reply, it's been sitting in
my 'to apply' mbox for awhile now).
Thanks,
Jesse
next prev parent reply other threads:[~2008-10-10 16:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-29 21:03 [PATCH] PCI probing debug message uniformization Vincent Legoll
2008-10-02 18:46 ` Jesse Barnes
2008-10-02 18:59 ` Bjorn Helgaas
2008-10-03 9:14 ` Vincent Legoll
2008-10-03 18:13 ` Vincent Legoll
2008-10-03 18:57 ` Bjorn Helgaas
2008-10-03 22:50 ` Vincent Legoll
2008-10-10 16:07 ` Jesse Barnes [this message]
2008-10-12 10:26 ` Vincent Legoll
2008-10-15 10:49 ` 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=200810100907.35798.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=bjorn.helgaas@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=vincent.legoll@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