From: Randy Dunlap <randy.dunlap@oracle.com>
To: David Miller <davem@davemloft.net>
Cc: dvomlehn@cisco.com, to@dvomlehn-lnx2.corp.sa.net,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
netdev@vger.kernel.org
Subject: Re: [PATCH 1/4][RFC] Introduction to sk_buff state checking
Date: Fri, 11 Jun 2010 13:46:17 -0700 [thread overview]
Message-ID: <20100611134617.b2c93c1b.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20100611.133811.52184181.davem@davemloft.net>
On Fri, 11 Jun 2010 13:38:11 -0700 (PDT) David Miller wrote:
>
> This is the second time you've submitted this patch set,
> it is also the second time that:
>
> 1) Your email client has emitted these strange
> "linux-kernel@vger.kernel.org"@cisco.com
> addresses.
>
> I saw that you were specifically notified about this
> problem during the previous submission.
>
> What did you do to try and correct it?
>
> 2) You are not CC:'ing the networking developer mailing
> list "netdev@vger.kernel.org" Many networking developers
> do not read linux-kernel, so by not CC:'ing that list
> you are not reaching the folks most capable of reviewing
> your patches.
>
> Please fix this up.
> --
Ack. Also this one:
----- The following addresses had permanent fatal errors -----
<to@dvomlehn-lnx2.corp.sa.net>
(reason: 550 Host unknown)
----- Transcript of session follows -----
550 5.1.2 <to@dvomlehn-lnx2.corp.sa.net>... Host unknown (Name server: dvomlehn-lnx2.corp.sa.net: host not found)
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-06-11 20:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-11 20:33 [PATCH 1/4][RFC] Introduction to sk_buff state checking David VomLehn
2010-06-11 20:38 ` David Miller
2010-06-11 20:46 ` Randy Dunlap [this message]
2010-06-11 20:50 ` David VomLehn
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=20100611134617.b2c93c1b.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=dvomlehn@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=to@dvomlehn-lnx2.corp.sa.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.