devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: Stephen Warren <swarren@wwwdotorg.org>,
	Laxman Dewangan <ldewangan@nvidia.com>
Cc: "alan@linux.intel.com" <alan@linux.intel.com>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"jslaby@suse.cz" <jslaby@suse.cz>,
	"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
	"devicetree-discuss@lists.ozlabs.org"
	<devicetree-discuss@lists.ozlabs.org>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH] serial: tegra: add serial driver
Date: Thu, 20 Dec 2012 01:09:02 +0000	[thread overview]
Message-ID: <20121220010902.2116B3E0AD7@localhost> (raw)
In-Reply-To: <50D1F22A.6090801@wwwdotorg.org>

On Wed, 19 Dec 2012 09:58:18 -0700, Stephen Warren <swarren@wwwdotorg.org> wrote:
> On 12/19/2012 07:15 AM, Laxman Dewangan wrote:
> > On Wednesday 19 December 2012 06:31 PM, Grant Likely wrote:
> >> On Mon, 17 Dec 2012 14:31:34 -0700, Stephen
> >> Warren<swarren@wwwdotorg.org>  wrote:
> >>> On 12/17/2012 10:10 AM, Grant Likely wrote:
> >>>> On Mon, 17 Dec 2012 17:40:49 +0530, Laxman
> >>>> Dewangan<ldewangan@nvidia.com>  wrote:
> >>>
> >>> Aren't we still supposed to support platform data so that it can
> >>> override what's in DT in order to fix up bad DTs? Or, has that
> >>> requirement been dropped. If it has, we can drop a bunch of code from a
> >>> variety of Tegra-specific drivers, I expect.
> >> Do you have an actual user for this? If not, then don't borrow trouble.
> >> Just drop it. Things like platform_data can always be added later only
> >> if it is needed.
> > 
> > Currently all our board supports DT. we are not using any driver
> > instantiated by board files.
> > I will remove the platform data for current patch and if it is require
> > then will add later with reasoning.
> > 
> > Hope this will be fine with Stephen also so that  this basic patch can
> > be included into tree soon.
> 
> I'm fine with it; it's just a change in policy that hadn't been
> communicated before.

Not really. For as long as I can remember there has been a strong bias
against unused code in the kernel. That goes for platform_data support
code as much as anything else.

What has been policy is that adding DT support must never break existing
non-DT support as long as non-DT booting is supported by a platform.

g.

  reply	other threads:[~2012-12-20  1:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-17 12:10 [PATCH] serial: tegra: add serial driver Laxman Dewangan
2012-12-17 15:13 ` Greg KH
2012-12-17 15:24 ` Rob Herring
2012-12-17 21:30   ` Stephen Warren
2012-12-17 17:10 ` Grant Likely
2012-12-17 21:31   ` Stephen Warren
2012-12-19 13:01     ` Grant Likely
2012-12-19 14:15       ` Laxman Dewangan
     [not found]         ` <50D1CC07.6070506-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-12-19 16:58           ` Stephen Warren
2012-12-20  1:09             ` Grant Likely [this message]
2012-12-17 18:23 ` Alan Cox
     [not found] ` <1355746249-15347-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-12-17 21:36   ` Stephen Warren
     [not found]     ` <50CF9043.8030308-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-12-17 21:58       ` Mitch Bradley
     [not found]         ` <50CF9580.4050300-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
2012-12-17 22:04           ` Stephen Warren
     [not found]             ` <50CF96D4.6010705-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-12-17 22:17               ` Mitch Bradley
2012-12-19 13:03                 ` Grant Likely
2012-12-17 21:55 ` Stephen Warren

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=20121220010902.2116B3E0AD7@localhost \
    --to=grant.likely@secretlab.ca \
    --cc=alan@linux.intel.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.cz \
    --cc=ldewangan@nvidia.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=rob.herring@calxeda.com \
    --cc=swarren@wwwdotorg.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).