All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jingoo Han <jg1.han@samsung.com>
To: 'Tushar Behera' <tushar.behera@linaro.org>,
	'Olof Johansson' <olof@lixom.net>
Cc: 'Arnd Bergmann' <arnd@arndb.de>,
	'Kevin Hilman' <khilman@linaro.org>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org,
	'Kukjin Kim' <kgene.kim@samsung.com>,
	'Doug Anderson' <dianders@chromium.org>,
	'Patch Tracking' <patches@linaro.org>,
	'Thomas Abraham' <thomas.abraham@linaro.org>,
	'Vivek Gautam' <gautam.vivek@samsung.com>,
	Jingoo Han <jg1.han@samsung.com>
Subject: Re: [PATCH] ARM: EXYNOS: Update defconfig for Arndale and Origen board
Date: Thu, 30 May 2013 16:05:54 +0900	[thread overview]
Message-ID: <000101ce5d04$20abb7a0$620326e0$@samsung.com> (raw)
In-Reply-To: <51A6C97A.6030306@linaro.org>

On Thursday, May 30, 2013 12:38 PM, Tushar Behera wrote:
>On 05/30/2013 12:16 AM, Olof Johansson wrote:
>> On Wed, May 29, 2013 at 2:33 AM, Jingoo Han <jg1.han@samsung.com> wrote:
>>
>>> However, Olof Johansson mentioned, 'drivers/platform/arm/board_arndale.c'
>>> would be a good alternative.
>>
>>
>> Whoa. I didn't quite realize what I proposed, or rather, how what I
>> proposed could be perceived. I take it back. :)

My original message is as below.

"However, as Olof Johansson mentioned, 'drivers/platform/arm/'
would be a good alternative."

Also, 'board_arndale.c' should not be mentioned.
Sorry for making confusion. :)

>>
>> We must _not_ introduce something that will be abused as a new home
>> for board file junk. If we do introduce a platform glue directory it
>> would need to be very limited in scope. Compare to what's in
>> drivers/platform/x86 today.
>>
>>
>> -Olof
>>
>
>This was my proof-of-concept for moving USB hub reset code out of USB
>driver. Verified that it works.

Thank you for your additional comment.

>
>I would wait for your patches for wifi-reset sequence and then will add
>hub-reset code for Arndale.

Yes, this way looks good.

Best regards,
Jingoo Han

>
>
>--
>Tushar Behera

WARNING: multiple messages have this Message-ID (diff)
From: jg1.han@samsung.com (Jingoo Han)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: EXYNOS: Update defconfig for Arndale and Origen board
Date: Thu, 30 May 2013 16:05:54 +0900	[thread overview]
Message-ID: <000101ce5d04$20abb7a0$620326e0$@samsung.com> (raw)
In-Reply-To: <51A6C97A.6030306@linaro.org>

On Thursday, May 30, 2013 12:38 PM, Tushar Behera wrote:
>On 05/30/2013 12:16 AM, Olof Johansson wrote:
>> On Wed, May 29, 2013 at 2:33 AM, Jingoo Han <jg1.han@samsung.com> wrote:
>>
>>> However, Olof Johansson mentioned, 'drivers/platform/arm/board_arndale.c'
>>> would be a good alternative.
>>
>>
>> Whoa. I didn't quite realize what I proposed, or rather, how what I
>> proposed could be perceived. I take it back. :)

My original message is as below.

"However, as Olof Johansson mentioned, 'drivers/platform/arm/'
would be a good alternative."

Also, 'board_arndale.c' should not be mentioned.
Sorry for making confusion. :)

>>
>> We must _not_ introduce something that will be abused as a new home
>> for board file junk. If we do introduce a platform glue directory it
>> would need to be very limited in scope. Compare to what's in
>> drivers/platform/x86 today.
>>
>>
>> -Olof
>>
>
>This was my proof-of-concept for moving USB hub reset code out of USB
>driver. Verified that it works.

Thank you for your additional comment.

>
>I would wait for your patches for wifi-reset sequence and then will add
>hub-reset code for Arndale.

Yes, this way looks good.

Best regards,
Jingoo Han

>
>
>--
>Tushar Behera

  reply	other threads:[~2013-05-30  7:05 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-10  6:49 [PATCH] ARM: EXYNOS: Update defconfig for Arndale and Origen board Tushar Behera
2013-05-10  6:49 ` Tushar Behera
2013-05-10 15:31 ` Doug Anderson
2013-05-10 15:31   ` Doug Anderson
2013-05-14  0:06 ` Kevin Hilman
2013-05-14  0:06   ` Kevin Hilman
2013-05-14  3:07   ` Tushar Behera
2013-05-14  3:07     ` Tushar Behera
2013-05-28 23:17     ` Olof Johansson
2013-05-28 23:17       ` Olof Johansson
2013-05-29  3:59       ` Tushar Behera
2013-05-29  3:59         ` Tushar Behera
2013-05-29  5:31         ` Olof Johansson
2013-05-29  5:31           ` Olof Johansson
2013-05-29  8:50           ` Tushar Behera
2013-05-29  8:50             ` Tushar Behera
2013-05-29  9:33             ` Jingoo Han
2013-05-29  9:33               ` Jingoo Han
2013-05-29 18:46               ` Olof Johansson
2013-05-29 18:46                 ` Olof Johansson
2013-05-30  3:37                 ` Tushar Behera
2013-05-30  3:37                   ` Tushar Behera
2013-05-30  7:05                   ` Jingoo Han [this message]
2013-05-30  7:05                     ` Jingoo Han
2013-05-30 13:10               ` Vivek Gautam
2013-05-30 13:10                 ` Vivek Gautam
2013-05-30 13:10                 ` Vivek Gautam
     [not found]                 ` <CAHbNUh0kWxqDMvLwE-_PKQVassDJvbgiCiDDNSHn9AW3md=A5A@mail.gmail.com>
2013-05-30 15:28                   ` Tushar Behera
2013-05-30 15:28                     ` Tushar Behera
2013-05-29 12:03           ` Tushar Behera
2013-05-29 12:03             ` Tushar Behera
2013-05-29 18:23           ` Kevin Hilman
2013-05-29 18:23             ` Kevin Hilman
2013-05-29 18:23             ` Kevin Hilman
2013-06-04 12:13           ` Mark Brown
2013-06-04 12:13             ` Mark Brown
2013-05-29 18:34         ` Kevin Hilman
2013-05-29 18:34           ` Kevin Hilman
2013-05-28 23:24 ` Olof Johansson
2013-05-28 23:24   ` Olof Johansson
2013-05-29  0:07   ` Kukjin Kim
2013-05-29  0:07     ` Kukjin Kim

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='000101ce5d04$20abb7a0$620326e0$@samsung.com' \
    --to=jg1.han@samsung.com \
    --cc=arnd@arndb.de \
    --cc=dianders@chromium.org \
    --cc=gautam.vivek@samsung.com \
    --cc=kgene.kim@samsung.com \
    --cc=khilman@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=patches@linaro.org \
    --cc=thomas.abraham@linaro.org \
    --cc=tushar.behera@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.