From: Hans de Goede <hdegoede@redhat.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] sunxi: Add new Mele_A1000G_quad defconfig
Date: Wed, 03 Jun 2015 16:09:14 +0200 [thread overview]
Message-ID: <556F0A8A.7070109@redhat.com> (raw)
In-Reply-To: <20150603125231.GB1728@bill-the-cat>
Hi,
On 03-06-15 14:52, Tom Rini wrote:
> On Wed, Jun 03, 2015 at 08:49:04AM +0100, Ian Campbell wrote:
>> On Tue, 2015-06-02 at 09:07 +0200, Hans de Goede wrote:
>>> So if there is no way to store this info in the defconfigs lets
>>> just leave it out and will point people to the wiki.
>>
>> Would it be totally mad to have a string CONFIG_BOARD_URL containing a
>> URL (e.g. to the relevant wiki page) which was printed on boot i.e. in a
>> "Board Info: http://...." type thing and/or in the help output?
>>
>> This started off as a thought on abusing Kconfig to somehow allow some
>> of this info to remain, but just that would be a step too far IMHO, but
>> if it also serves a (somewhat) practical purpose, then, maybe?
>>
>> (I'm not convinced myself, but thought I'd mention it).
>
> Ah, MAINTAINERS can help here. Checking out the kernel's copy:
>
> Descriptions of section entries:
>
> P: Person (obsolete)
> M: Mail patches to: FullName <address@domain>
> L: Mailing list that is relevant to this area
> W: Web-page with status/info
> ...
>
Ah yes the W: option in MAINTAINERS is indeed the best place to
stick URL-s, thanks for your input.
Regards,
Hans
next prev parent reply other threads:[~2015-06-03 14:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 15:01 [U-Boot] [PATCH] sunxi: Add new Mele_A1000G_quad defconfig Hans de Goede
2015-06-01 18:12 ` Ian Campbell
2015-06-01 18:19 ` Hans de Goede
2015-06-01 20:46 ` Tom Rini
2015-06-02 7:07 ` Hans de Goede
2015-06-02 13:35 ` Tom Rini
2015-06-03 7:49 ` Ian Campbell
2015-06-03 8:15 ` Hans de Goede
2015-06-03 12:52 ` Tom Rini
2015-06-03 14:09 ` Hans de Goede [this message]
2015-06-03 19:08 ` Ian Campbell
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=556F0A8A.7070109@redhat.com \
--to=hdegoede@redhat.com \
--cc=u-boot@lists.denx.de \
/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