From: David Miller <davem@davemloft.net>
To: joe@perches.com
Cc: heder@google.com, lvs-devel@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
jengelh@medozas.de
Subject: Re: [PATCH v2 2/2] IPVS: use pr_err and friends instead of IP_VS_ERR and friends
Date: Thu, 30 Jul 2009 14:29:06 -0700 (PDT) [thread overview]
Message-ID: <20090730.142906.266849967.davem@davemloft.net> (raw)
In-Reply-To: <1248814615.18284.22.camel@Joe-Laptop.home>
From: Joe Perches <joe@perches.com>
Date: Tue, 28 Jul 2009 13:56:55 -0700
> On Tue, 2009-07-28 at 22:35 +0200, Hannes Eder wrote:
>> Since pr_err and friends is used instead of printk there is not point
>> in keeping IP_VS_ERR and friends.
>> + pr_err("Schedule: port zero only supported "
>> + "in persistent services, "
>> + "check your ipvs configuration\n");
>
> You might consider ignoring the checkpatch 80 char limit here
> and consolidate the message into a single string.
I don't think this is such a big deal.
>> - IP_VS_ERR("ip_vs_svc_unhash(): request for unhash flagged, "
>> - "called from %p\n", __builtin_return_address(0));
>> + pr_err("ip_vs_svc_unhash(): request for unhash flagged, "
>> + "called from %p\n", __builtin_return_address(0));
>
> Maybe use something like:
> "%s(): <foo> called from %pf",
> __func__, __builtin_return_address(0)
>
However I do agree that this change should be made.
prev parent reply other threads:[~2009-07-30 21:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 20:35 [PATCH v2 0/2] IPVS: make use of pr_fmt and friends Hannes Eder
2009-07-28 20:35 ` [PATCH v2 1/2] IPVS: use pr_fmt Hannes Eder
2009-07-30 21:30 ` David Miller
2009-07-28 20:35 ` [PATCH v2 2/2] IPVS: use pr_err and friends instead of IP_VS_ERR and friends Hannes Eder
2009-07-28 20:56 ` Joe Perches
2009-07-28 23:33 ` Simon Horman
2009-07-30 21:29 ` David Miller [this message]
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=20090730.142906.266849967.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=heder@google.com \
--cc=jengelh@medozas.de \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lvs-devel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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