[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20150413.132438.259409084264003362.davem@davemloft.net>
Date: Mon, 13 Apr 2015 13:24:38 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: jiri@...nulli.us
Cc: sfeldma@...il.com, netdev@...r.kernel.org,
roopa@...ulusnetworks.com, f.fainelli@...il.com,
gospo@...ulusnetworks.com
Subject: Re: [patch net-next 1/2] switchdev: s/netdev_switch_/switchdev_/
From: Jiri Pirko <jiri@...nulli.us>
Date: Mon, 13 Apr 2015 17:19:32 +0200
> Mon, Apr 13, 2015 at 05:06:04PM CEST, sfeldma@...il.com wrote:
>>On Mon, Apr 13, 2015 at 8:01 AM, Jiri Pirko <jiri@...nulli.us> wrote:
>>> Mon, Apr 13, 2015 at 04:48:51PM CEST, sfeldma@...il.com wrote:
>>>>On Mon, Apr 13, 2015 at 7:14 AM, Jiri Pirko <jiri@...nulli.us> wrote:
>>>>> Turned out that "switchdev" sticks. So just unify all releated terms to
>>>>> use this prefix.
>>>>>
>>>>> Signed-off-by: Jiri Pirko <jiri@...nulli.us>
>>>>
>>>>NACK. I'm right in the middle of a large patchset which touches all
>>>>of these files in all of those places and a rename before mine will
>>>>create a git merge nightmare. Please wait to post any rename patches
>>>>until after my set goes in.
>>>
>>> Makes sense to me to rename first so you can add new functions with
>>> "switchdev_" prefix on top of that.
>>
>>I am renaming, to swdev_ and all new stuff gets swdev_ prefix. You're
>>welcome to change the prefix after my patch set goes in but don't try
>>to slip it under as it totally messes up my patch stack.
>
> Scott, at least please use "switchdev_" prefix for your new stuff so it
> does not have to be renamed right after.
Scott, I think Jiri's request is reasonable.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists