From: David Miller <davem@davemloft.net>
To: amit.salecha@qlogic.com
Cc: netdev@vger.kernel.org, ameen.rahman@qlogic.com,
anirban.chakraborty@qlogic.com, stable@kernel.org
Subject: Re: [PATCH NET-2.6 1/1] qlcnic: limit skb frags for non tso packet
Date: Tue, 12 Apr 2011 13:55:22 -0700 (PDT) [thread overview]
Message-ID: <20110412.135522.71113479.davem@davemloft.net> (raw)
In-Reply-To: <1302592781-13881-2-git-send-email-amit.salecha@qlogic.com>
From: Amit Kumar Salecha <amit.salecha@qlogic.com>
Date: Tue, 12 Apr 2011 00:19:41 -0700
> <<< No Message Collected >>>
Can you PLEASE fix your email.
PLEASE?
Yesterday you spammed us all, and today you've sent three postings
with this subject line.
1) One with the patch, and the proper set of CC:'s (myself, other
qlogic engineers, netdev, and stable)
2) One with the patch, and a too short CC: list (only netdev and
stable)
3) And now this email with no actual content and a weird message.
I really can't spend my afternoons sifting through the emails that
spam from qlogic, trying to figure out which ones I should pay
attention to for review, and which ones are spam.
Please resend properly any patches you actually want me to pay
attention to.
If you cannot make sure at this time that the patches will be sent
without incident, sit on them until you can.
Thank you.
next prev parent reply other threads:[~2011-04-12 20:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 7:19 [PATCH NET-2.6 0/1]qlcnic: bug fix Amit Kumar Salecha
2011-04-12 7:19 ` [PATCH NET-2.6 1/1] qlcnic: limit skb frags for non tso packet Amit Kumar Salecha
2011-04-12 20:55 ` David Miller [this message]
2011-04-13 2:01 ` Amit Salecha
2011-04-13 3:42 ` [stable] " Greg KH
2011-04-13 5:56 ` Amit Salecha
2011-04-13 14:03 ` Greg KH
2011-04-13 15:59 ` Amit Salecha
2011-04-13 16:15 ` Greg KH
2011-04-14 5:22 ` [stable] " Amit Salecha
2011-04-14 20:09 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2011-04-12 8:15 Amit Kumar Salecha
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=20110412.135522.71113479.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ameen.rahman@qlogic.com \
--cc=amit.salecha@qlogic.com \
--cc=anirban.chakraborty@qlogic.com \
--cc=netdev@vger.kernel.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).