From: "David S. Miller" <davem@redhat.com>
To: Andi Kleen <ak@muc.de>
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH] Limit SO_BSDCOMPAT warning
Date: Fri, 24 Oct 2003 19:37:26 -0700 [thread overview]
Message-ID: <20031024193726.0c269b60.davem@redhat.com> (raw)
In-Reply-To: <20031024205707.GA1072@averell>
On Fri, 24 Oct 2003 22:57:07 +0200
Andi Kleen <ak@muc.de> wrote:
> Warning a few times for each process is enough.
Ok, I'll apply this. I like this version of a patch limiting this
message, compared to the others that have been submitted, because it
still ensures that every program that has the problem will show up at
least one time in the logs.
Thanks Andi.
prev parent reply other threads:[~2003-10-25 2:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-24 20:57 [PATCH] Limit SO_BSDCOMPAT warning Andi Kleen
2003-10-25 2:37 ` David S. 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=20031024193726.0c269b60.davem@redhat.com \
--to=davem@redhat.com \
--cc=ak@muc.de \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).