linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: mmp: support pinctrl single in brownstone
Date: Mon, 19 Nov 2012 21:57:00 -0700	[thread overview]
Message-ID: <50AB0D9C.5060101@wwwdotorg.org> (raw)
In-Reply-To: <CAN1soZyTad0QVt-oKM24XiHYruyFx5MTiu2+ytGL5RNv-Pqonw@mail.gmail.com>

On 11/19/2012 05:52 PM, Haojian Zhuang wrote:
> On Tue, Nov 20, 2012 at 5:42 AM, Stephen Warren <swarren@wwwdotorg.org> wrote:
>> On 11/16/2012 12:02 AM, Haojian Zhuang wrote:
>>> Support pinctrl-single driver in brownstone platform with DT.
>>
>>> diff --git a/arch/arm/boot/dts/mmp2-brownstone.dts b/arch/arm/boot/dts/mmp2-brownstone.dts
>>
>>>       chosen {
>>> -             bootargs = "console=ttyS2,38400 root=/dev/nfs nfsroot=192.168.1.100:/nfsroot/ ip=192.168.1.101:192.168.1.100::255.255.255.0::eth0:on";
>>> +             bootargs = "console=ttyS2,38400 root=/dev/nfs nfsroot=192.168.1.100:/nfsroot/ ip=192.168.1.101:192.168.1.100::255.255.255.0::eth0:on earlyprintk";
>>
>> That seems unrelated.
>>
> But it's helpful on debug. Should I remove this? I prefer that I could
> keep this.
> 
> Since I want to watch the whole log before console is enabled.

It should be a separate patch at least.

  reply	other threads:[~2012-11-20  4:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-16  7:02 [PATCH 1/2] ARM: dts: support pinctrl single in aspenite Haojian Zhuang
2012-11-16  7:02 ` [PATCH 2/2] ARM: mmp: support pinctrl single in brownstone Haojian Zhuang
2012-11-19 21:42   ` Stephen Warren
2012-11-20  0:52     ` Haojian Zhuang
2012-11-20  4:57       ` Stephen Warren [this message]
2012-11-19 21:41 ` [PATCH 1/2] ARM: dts: support pinctrl single in aspenite Stephen Warren
2012-11-20  0:50   ` Haojian Zhuang

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=50AB0D9C.5060101@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=linux-arm-kernel@lists.infradead.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).