linux-tegra.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laxman Dewangan <ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: "linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org"
	<linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
	"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
	<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
	"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] ARM: tegra: dts: add aliases and DMA requestor for serial controller
Date: Tue, 25 Dec 2012 15:13:47 +0530	[thread overview]
Message-ID: <50D97553.80001@nvidia.com> (raw)
In-Reply-To: <50D93AB6.7040905-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>

On Tuesday 25 December 2012 11:03 AM, Stephen Warren wrote:
> On 12/22/2012 01:15 PM, Laxman Dewangan wrote:
>
>> This way it is straight
>> forward for the uart user to directly see the uart instance on board and
>> decide the port number rather than going to what are other uart and
>> their corresponding driver.
> Still, there is some precedent in the kernel for your approach. So, I
> guess we can go ahead with using the aliases as-is.
>

So can I assume this patch is fine and I need not to re-spin it for 
removing aliases?

  parent reply	other threads:[~2012-12-25  9:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-19  6:31 [PATCH] ARM: tegra: dts: add aliases and DMA requestor for serial controller Laxman Dewangan
     [not found] ` <1355898671-3960-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-12-19 17:00   ` Stephen Warren
     [not found]     ` <50D1F2CB.3090206-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-12-20  6:15       ` Laxman Dewangan
     [not found]         ` <50D2AD02.6060101-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-12-20 17:03           ` Stephen Warren
     [not found]             ` <50D344E9.70305-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-12-21  4:18               ` Laxman Dewangan
     [not found]                 ` <50D3E320.2090804-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-12-21 20:50                   ` Stephen Warren
     [not found]                     ` <50D4CBB0.7080603-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-12-22 20:15                       ` Laxman Dewangan
     [not found]                         ` <50D614D9.8020106-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-12-25  5:33                           ` Stephen Warren
     [not found]                             ` <50D93AB6.7040905-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-12-25  9:43                               ` Laxman Dewangan [this message]
2012-12-22 20:15                       ` Laxman Dewangan
2013-01-02 19:19   ` 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=50D97553.80001@nvidia.com \
    --to=ldewangan-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.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).