All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Hellstrom <daniel@gaisler.com>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH] sparc,leon: support for GRPCI1 PCI host bridge controller
Date: Mon, 04 Mar 2013 07:30:20 +0000	[thread overview]
Message-ID: <51344D8C.7080403@gaisler.com> (raw)
In-Reply-To: <1362061978-1964-1-git-send-email-daniel@gaisler.com>

On 03/01/2013 10:39 PM, David Miller wrote:
> From: Sam Ravnborg <sam@ravnborg.org>
> Date: Fri, 1 Mar 2013 19:51:46 +0100
>
>>>>>    	default y
>>>>>    +config GRPCI1
>>>> I see we do not do so with GRPCI2 - but please prefix
>>>> all SPARC specific kconfig symbols with SPARC_
>>> I can only see SPARC_LED and SPARC_LEON in arch/sparc/Kconfig following that naming convention.
>>>   Would it be more correct to call it LEON_GRPCI1? I see there are some SUN_ and US3_ names.
>> sparc is not a good example here :-(
>> For the new architectures I have reviewed recently all their arch specific symbols
>> has been prefixed with the abbreviated arch name.
>> And sparc specific symbols we add shall follow the same rule.
>>
>> I may fix up the other sparc specific symbols one day too, but it is low on
>> my todo list.
>> On the other hand using the name SPARC_LEON_xxx is too specific.
>> We already should know what it is from the SPARC_GRPCI part of the name.
> I agree with Sam, prefix all your new Kconfig symbols with SPARC_*, thanks.

Ok, that makes sense. I will update the two patches and resend.

Thanks,
Daniel

      parent reply	other threads:[~2013-03-04  7:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-28 14:32 [PATCH] sparc,leon: support for GRPCI1 PCI host bridge controller Daniel Hellstrom
2013-02-28 21:22 ` Sam Ravnborg
2013-03-01  8:20 ` Daniel Hellstrom
2013-03-01 18:51 ` Sam Ravnborg
2013-03-01 21:39 ` David Miller
2013-03-04  7:30 ` Daniel Hellstrom [this message]

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=51344D8C.7080403@gaisler.com \
    --to=daniel@gaisler.com \
    --cc=sparclinux@vger.kernel.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.