All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Paul Walmsley <pwalmsley-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: Tegra baseline test results for v3.10-rc1
Date: Thu, 06 Jun 2013 09:58:14 -0600	[thread overview]
Message-ID: <51B0B196.3040400@wwwdotorg.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1306060421250.15042-rwI8Ez+7Ko+d5PgPZx9QOdBPR1lH4CV8@public.gmane.org>

On 06/05/2013 10:34 PM, Paul Walmsley wrote:
> Hi Stephen,
> 
> thanks very much for the review -
> 
> On Wed, 5 Jun 2013, Stephen Warren wrote:
> 
>> On 06/04/2013 11:59 PM, Paul Walmsley wrote:
>>>
>>> Here are some basic Tegra test results for Linux v3.10-rc1.
>>> Logs and other details at:
...
>> I'm curious what the difference is between the "t33beaver" and
>> "tegra30-beaver" path entries is, in the following URL:
>>
>> http://www.pwsan.com/tegra/testlogs/test_v3.10-rc1/20130519152115/boot/t33beaver/tegra30-beaver/
>>
>> It might be better to call this board just "tegra30-beaver" for
>> consistency with other upstream tools like cbootimage-configs and the
>> DTB filename.
> 
> In the boot test environment here, "t33beaver" uniquely identifies the 
> board, while "tegra30-beaver" identifies the DTB used to boot it.  
> So if an alternate DTB were used, the boot test path would be:
> 
> ../boot/t33beaver/tegra30-beaver-alternate/
> 
> If it's important to you, I'll change it.  Otherwise, I'd prefer not to 
> call the board 'tegra30-beaver' -- mostly to avoid confusing myself 
> between the board name and the DTB name :-)

Could you name the directories
.../boot/board-tegra30-beaver/tegra30-beaver.dtb/ or
../boot/board-tegra30-beaver/tegra30-beaver-alternate.dtb/? I'd really
love not to propagate a different set of names for the boards.

WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: Tegra baseline test results for v3.10-rc1
Date: Thu, 06 Jun 2013 09:58:14 -0600	[thread overview]
Message-ID: <51B0B196.3040400@wwwdotorg.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1306060421250.15042@utopia.booyaka.com>

On 06/05/2013 10:34 PM, Paul Walmsley wrote:
> Hi Stephen,
> 
> thanks very much for the review -
> 
> On Wed, 5 Jun 2013, Stephen Warren wrote:
> 
>> On 06/04/2013 11:59 PM, Paul Walmsley wrote:
>>>
>>> Here are some basic Tegra test results for Linux v3.10-rc1.
>>> Logs and other details at:
...
>> I'm curious what the difference is between the "t33beaver" and
>> "tegra30-beaver" path entries is, in the following URL:
>>
>> http://www.pwsan.com/tegra/testlogs/test_v3.10-rc1/20130519152115/boot/t33beaver/tegra30-beaver/
>>
>> It might be better to call this board just "tegra30-beaver" for
>> consistency with other upstream tools like cbootimage-configs and the
>> DTB filename.
> 
> In the boot test environment here, "t33beaver" uniquely identifies the 
> board, while "tegra30-beaver" identifies the DTB used to boot it.  
> So if an alternate DTB were used, the boot test path would be:
> 
> ../boot/t33beaver/tegra30-beaver-alternate/
> 
> If it's important to you, I'll change it.  Otherwise, I'd prefer not to 
> call the board 'tegra30-beaver' -- mostly to avoid confusing myself 
> between the board name and the DTB name :-)

Could you name the directories
.../boot/board-tegra30-beaver/tegra30-beaver.dtb/ or
../boot/board-tegra30-beaver/tegra30-beaver-alternate.dtb/? I'd really
love not to propagate a different set of names for the boards.

  parent reply	other threads:[~2013-06-06 15:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-05  5:59 Tegra baseline test results for v3.10-rc1 Paul Walmsley
2013-06-05  5:59 ` Paul Walmsley
     [not found] ` <alpine.DEB.2.02.1306050558430.13098-rwI8Ez+7Ko+d5PgPZx9QOdBPR1lH4CV8@public.gmane.org>
2013-06-05 15:17   ` Stephen Warren
2013-06-05 15:17     ` Stephen Warren
     [not found]     ` <51AF5698.5050106-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-06-06  4:34       ` Paul Walmsley
2013-06-06  4:34         ` Paul Walmsley
     [not found]         ` <alpine.DEB.2.02.1306060421250.15042-rwI8Ez+7Ko+d5PgPZx9QOdBPR1lH4CV8@public.gmane.org>
2013-06-06 15:58           ` Stephen Warren [this message]
2013-06-06 15:58             ` Stephen Warren
     [not found]             ` <51B0B196.3040400-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-06-11 12:26               ` Paul Walmsley
2013-06-11 12:26                 ` Paul Walmsley

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=51B0B196.3040400@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=pwalmsley-DDmLM1+adcrQT0dZR+AlfA@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 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.