linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: tomoya.rohm@gmail.com
Cc: jeffrey.t.kirsher@intel.com, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, qi.wang@intel.com, yong.y.wang@intel.com,
	joel.clark@intel.com, kok.howg.ewe@intel.com
Subject: Re: [PATCH 1/3] ethernet/pch_gbe: Change company name OKI SEMICONDUCTOR to LAPIS Semiconductor
Date: Mon, 30 Jan 2012 12:52:19 -0500 (EST)	[thread overview]
Message-ID: <20120130.125219.2077768183344205118.davem@davemloft.net> (raw)
In-Reply-To: <1327643159-1302-1-git-send-email-tomoya.rohm@gmail.com>


Sorry, we're not going to get into this pattern where we move drivers
around in the tree every time the company that produces the chip
changes it's name.

If we did this then certain drivers will have moved 5 or more times
since the beginning of the Linux kernel, and there is nothing to be
gained from that except confusion.

In fact more valuable thing to do is to refer to both the old and the
new name, rather than just the new one or just the old one.  Because
you now have two sets of users, one very large set which is familiar
with the old name and a smaller set which will only know about the new
name.

Frankly, I would just leave everything alone except perhaps adding a
mention of the new name (and not deleting the old name) in the Kconfig
help text.

  parent reply	other threads:[~2012-01-30 17:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-27  5:45 [PATCH 1/3] ethernet/pch_gbe: Change company name OKI SEMICONDUCTOR to LAPIS Semiconductor Tomoya MORINAGA
2012-01-27  5:45 ` [PATCH 2/3] ethernet/pch_gbe: add Intel EG20T PCH Tomoya MORINAGA
2012-01-27  5:45 ` [PATCH 3/3] ethernet: Change author mail address Tomoya MORINAGA
2012-01-30 17:52 ` David Miller [this message]
2012-01-31  0:35   ` [PATCH 1/3] ethernet/pch_gbe: Change company name OKI SEMICONDUCTOR to LAPIS Semiconductor Tomoya MORINAGA
2012-01-31  1:19     ` David Miller
2012-01-31 10:41       ` Tomoya MORINAGA
2012-02-22  5:03         ` Tomoya MORINAGA

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=20120130.125219.2077768183344205118.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=joel.clark@intel.com \
    --cc=kok.howg.ewe@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=qi.wang@intel.com \
    --cc=tomoya.rohm@gmail.com \
    --cc=yong.y.wang@intel.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).