linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Mathieu Desnoyers <compudj@krystal.dyndns.org>
Cc: linux arch <linux-arch@vger.kernel.org>,
	Randy Dunlap <rdunlap@xenotime.net>
Subject: Re: HAVE or ARCH_HAS or ARCH_SUPPORTS and use of select
Date: Thu, 15 Nov 2007 19:14:51 +0100	[thread overview]
Message-ID: <20071115181451.GA23914@uranus.ravnborg.org> (raw)
In-Reply-To: <20071115122151.GA10359@Krystal>

On Thu, Nov 15, 2007 at 07:21:51AM -0500, Mathieu Desnoyers wrote:
> 
> FWIW, I've used "NEED_*" in my LTTng patchset to specify when an
> architecture needs support from an architecture independent module. (it
> could be an alternative to USE_*).

The situations we need to cover are:

1) An architecture uses or support a generic implementation
   Examples: KPROBES, GENERIC_TIME

2) An architecture uses a specific functionality
   Examples: MMU

3) Architecture provide a specific functionality
   Examples: ARCH_HAS_ILOG2_U32, ARCH_HAS_ILOG2_U64

4) A driver is supported by a subset of the architectures
   Example: config EDAC
                   depends on X86 || PPC


I'm very tempted to go with the suggestion of Russell and
say that the naming is the very generic:
HAVE_<config-symbol>

We know it from the auto-tools (albeit that could be a reason to avoid it)
And we can hardly put wrong interpretations in the HAVE_ thing.

	Sam

  reply	other threads:[~2007-11-15 18:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-15  9:02 HAVE or ARCH_HAS or ARCH_SUPPORTS and use of select Sam Ravnborg
2007-11-15 10:26 ` Russell King
2007-11-15 12:21 ` Mathieu Desnoyers
2007-11-15 18:14   ` Sam Ravnborg [this message]
2007-11-15 22:13     ` Geert Uytterhoeven
2007-11-15 22:56       ` David Howells

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=20071115181451.GA23914@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=compudj@krystal.dyndns.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /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;
as well as URLs for NNTP newsgroup(s).