From: David Miller <davem@davemloft.net>
To: heder@google.com
Cc: lvs-devel@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, joe@perches.com,
jengelh@medozas.de, horms@verge.net.au
Subject: Re: [PATCH v3 2/2] IPVS: use pr_err and friends instead of IP_VS_ERR and friends
Date: Sun, 02 Aug 2009 12:55:35 -0700 (PDT) [thread overview]
Message-ID: <20090802.125535.13404927.davem@davemloft.net> (raw)
In-Reply-To: <20090731113155.22420.59863.stgit@jazzy.zrh.corp.google.com>
From: Hannes Eder <heder@google.com>
Date: Fri, 31 Jul 2009 13:31:55 +0200
> Since pr_err and friends are used instead of printk there is not point
> in keeping IP_VS_ERR and friends. Furthermore make use of '__func__'
> instead of hard coded function names.
>
> Signed-off-by: Hannes Eder <heder@google.com>
This patch does not apply to net-next-2.6.
parent reply other threads:[~2009-08-02 19:55 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20090731113155.22420.59863.stgit@jazzy.zrh.corp.google.com>]
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=20090802.125535.13404927.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=heder@google.com \
--cc=horms@verge.net.au \
--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