netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: luka@openwrt.org
Cc: netdev@vger.kernel.org, abrodkin@synopsys.com
Subject: Re: [PATCH] ethernet/arc/arc_emac: drop redundant mac address check
Date: Mon, 28 Oct 2013 23:48:42 -0400 (EDT)	[thread overview]
Message-ID: <20131028.234842.1406231268962965513.davem@davemloft.net> (raw)
In-Reply-To: <1383010340-26445-1-git-send-email-luka@openwrt.org>


I've seen you use three inconsistent Subject prefixes here, pick a scheme
and stick to it please!

First patch was:

netdev: ${driver_name}:

Second patch was:

net: ${driver_name}:

Third patch was:

patch/to/driver/directory:

This is really not acceptable.  Just using "${driver_name}: " is good
enough.

  reply	other threads:[~2013-10-29  3:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-29  1:32 [PATCH] ethernet/arc/arc_emac: drop redundant mac address check Luka Perkov
2013-10-29  3:48 ` David Miller [this message]
2013-10-29  9:10   ` Luka Perkov

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=20131028.234842.1406231268962965513.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=abrodkin@synopsys.com \
    --cc=luka@openwrt.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;
as well as URLs for NNTP newsgroup(s).