public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@uclinux.org>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-m68k@lists.linux-m68k.org
Subject: Re: m68k: five unused boards in Kconfig.machine
Date: Mon, 25 Mar 2013 16:43:50 +1000	[thread overview]
Message-ID: <514FF226.3050507@uclinux.org> (raw)
In-Reply-To: <1363868258.1390.129.camel@x61.thuisdomein>

Hi Paul,

On 21/03/13 22:17, Paul Bolle wrote:
> 0) These five Kconfig entries in arch/m68k/Kconfig.machine are entirely
> unused:
>      config UC5272
>      config UC5282
>      config SOM5282EM
>      config COBRA5329
>      config SNAPGEAR
>
> 1) I think that these can be removed. But I recall from an earlier
> thread (in 2011) that Greg wanted to keep SOM5282EM:
>      Although it isn't used inside the code it does let the configurer
>      know that this specific board is supported.
>
> 2) Would it be acceptable to remove these five Kconfig entries but add
> text to the prompts or the help strings of some other entries to
> indicate support?

I have been moving the underlying code to be more generic in
its support of various ColdFire boards. I am a lot more comfortable
now removing the specific board names if we really don't have
anything specific keyed on them.

Regards
Greg

  reply	other threads:[~2013-03-25  6:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-21 12:17 m68k: five unused boards in Kconfig.machine Paul Bolle
2013-03-25  6:43 ` Greg Ungerer [this message]
2013-05-16 20:11   ` [PATCH] m68k: remove 15 " Paul Bolle
2013-05-17  7:59     ` [PATCH v2] m68k: remove 16 " Paul Bolle
2013-05-21 12:42       ` Greg Ungerer
2013-08-05  4:04       ` Greg Ungerer

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=514FF226.3050507@uclinux.org \
    --to=gerg@uclinux.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=pebolle@tiscali.nl \
    /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