From: Luka Perkov <luka@openwrt•org>
To: David Miller <davem@davemloft•net>
Cc: netdev@vger•kernel.org, abrodkin@synopsys•com
Subject: Re: [PATCH] ethernet/arc/arc_emac: drop redundant mac address check
Date: Tue, 29 Oct 2013 10:10:28 +0100 [thread overview]
Message-ID: <20131029091028.GA18147@w500.lan> (raw)
In-Reply-To: <20131028.234842.1406231268962965513.davem@davemloft.net>
Hi David,
On Mon, Oct 28, 2013 at 11:48:42PM -0400, David Miller wrote:
> 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:
True. I have sent it that way because I've followed the commit
schematics of each driver individually.
> This is really not acceptable. Just using "${driver_name}: " is good
> enough.
It's not a problem to resend them... But I'm wondering should this be
squashed into one patch?
Luka
prev parent reply other threads:[~2013-10-29 9:10 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
2013-10-29 9:10 ` Luka Perkov [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=20131029091028.GA18147@w500.lan \
--to=luka@openwrt$(echo .)org \
--cc=abrodkin@synopsys$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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