From: David Miller <davem@davemloft.net>
To: peppe.cavallaro@st.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 1/4] stmmac: remove two useless initialisation
Date: Wed, 23 May 2012 02:42:11 -0400 (EDT) [thread overview]
Message-ID: <20120523.024211.816676351593259308.davem@davemloft.net> (raw)
In-Reply-To: <1337754964-21754-1-git-send-email-peppe.cavallaro@st.com>
You really need to post your patches properly.
In particular, you need to indicate, either in an initial "[PATCH 0/N]"
posting, or in the subject lines of that patch, exactly what tree
you are targetting.
And if this is meant for net-next, I told you specifically that net-next
is not open right now and you need to submit this later when I make
the announcement here that it is open.
We are in the middle of the merge window, and therefore you should only
be submitting bug fixes against the 'net' tree.
It is extremely irritating that, when I go out of my way to make
announcements here on this list, multiple times, about what kind of
patches are appropriate and what kinds are not, and yet people still
do not listen and they still submit any old crap they feel like
submitting.
People need to stop this, now.
Pay attention to the development state, and follow the rules,
otherwise you'll royally piss me off and I'll ignore your patches
completely.
Thanks.
next prev parent reply other threads:[~2012-05-23 6:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 6:36 [PATCH 1/4] stmmac: remove two useless initialisation Giuseppe CAVALLARO
2012-05-23 6:36 ` [PATCH 2/4] stmmac: fix driver's doc when run kernel-doc script Giuseppe CAVALLARO
2012-05-23 6:36 ` [PATCH 3/4] stmmac: fix driver Kconfig when built as module Giuseppe CAVALLARO
2012-05-23 6:36 ` [PATCH 4/4] stmmac: update driver's doc Giuseppe CAVALLARO
2012-05-23 6:42 ` David Miller [this message]
2012-05-23 7:38 ` [PATCH 1/4] stmmac: remove two useless initialisation Giuseppe CAVALLARO
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=20120523.024211.816676351593259308.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.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).