All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: Re: [pinmux scripts PATCH 2/4] Board CSV import: Put full CSV filename in data structure
Date: Wed, 15 Oct 2014 13:20:43 -0600	[thread overview]
Message-ID: <543EC90B.4070705@wwwdotorg.org> (raw)
In-Reply-To: <1413306680-27330-2-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>

On 10/14/2014 11:11 AM, Stephen Warren wrote:
> From: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
>
> Putting the whole filename in to the data structure allows us to keep
> different CSV files in different directories. This will allow explicit
> separation of public and private CSV files.
>
> The per-board data is also modified to be a dictionary so that additional
> fields can be stored in the future.

I have applied this series.

>   supported_boards = {
> -    'jetson-tk1': 'T124_customer_pinmux_PM375_30Apr2014_v2.csv', # worksheet PM375Beaver_Configuration
> -    'norrin': 'PM370_T124_customer_pinmux_1.1.csv', # worksheet Customer_Configuration
> -    'venice2': 'Venice2_T124_customer_pinmux_based_on_P4_rev47_2013-07-12.csv', # worksheet Customer_Configuration
> +    'jetson-tk1': {
> +        # T124_customer_pinmux_PM375_30Apr2014_v2.xlsm worksheet PM375Beaver_Configuration
> +        # T124_customer_pinmux.xlsm worksheet Jetson TK1 Configuration
> +        # Jetson_TK1_customer_pinmux_release.xlsm worksheet Jetson TK1 Configuration
> +        'filename': 'csv/jetson-tk1.csv', # worksheet PM375Beaver_Configuration

I removed that stale comment on the filename: line, and added a note at 
the end of all the comments in this data structure re: which files use 
0- vs. 1-based rsvd numbering.

  parent reply	other threads:[~2014-10-15 19:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-14 17:11 [pinmux scripts PATCH 1/4] Board CSV import: Support all Tegra124 OD pins Stephen Warren
     [not found] ` <1413306680-27330-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-10-14 17:11   ` [pinmux scripts PATCH 2/4] Board CSV import: Put full CSV filename in data structure Stephen Warren
     [not found]     ` <1413306680-27330-2-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-10-15 19:20       ` Stephen Warren [this message]
2014-10-14 17:11   ` [pinmux scripts PATCH 3/4] Board CSV import: Support either 0- or 1-based RSVD numbers Stephen Warren
2014-10-14 17:11   ` [pinmux scripts PATCH 4/4] Board CSV Import: Allow board configuration overrides on cmdline 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=543EC90B.4070705@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=swarren-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.