All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Daniel Drake <dsd@gentoo.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH/RFC] introduce ARCH_CAN_UNALIGNED_ACCESS Kconfig symbol
Date: Thu, 20 Mar 2008 19:13:10 +0100	[thread overview]
Message-ID: <20080320181310.GA17884@uranus.ravnborg.org> (raw)
In-Reply-To: <1206023695.16475.137.camel@johannes.berg>

On Thu, Mar 20, 2008 at 03:34:55PM +0100, Johannes Berg wrote:
> In many cases, especially in networking, it can be beneficial to
> know at compile time whether the architecture can do unaligned
> accesses. This patch introduces a new Kconfig symbol
> 	ARCH_CAN_UNALIGNED_ACCESS

Can we please have a single symbol defined and name it:
HAVE_*

Then the architectures that HAVE this feature can select the symbol.

So somewhere in maybe lib/Kconfig or maybe arch/Kconfig add:

config HAVE_UNALIGNED_ACCESS_SUPPORT
	bool

And then for x86 select the symbol:

 config X86
+	select HAVE_UNALIGNED_ACCESS_SUPPORT


This follows the suggestion as available in
Documentation/kbuild/kconfig-language.txt

	Sam

  parent reply	other threads:[~2008-03-20 18:12 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-20 14:34 [PATCH/RFC] introduce ARCH_CAN_UNALIGNED_ACCESS Kconfig symbol Johannes Berg
2008-03-20 14:39 ` Will Newton
2008-03-20 14:39   ` Will Newton
2008-03-20 14:58   ` Johannes Berg
2008-03-20 14:58     ` Johannes Berg
2008-03-20 18:13 ` Sam Ravnborg [this message]
2008-03-20 18:35   ` Johannes Berg
2008-03-20 18:35     ` Johannes Berg
2008-03-20 18:39   ` [PATCH/RFC v2] " Johannes Berg
2008-03-20 18:45     ` [PATCH/RFC v3] " Johannes Berg
2008-03-20 18:45       ` Johannes Berg
2008-03-20 19:09       ` Harvey Harrison
2008-03-20 19:12         ` Johannes Berg
2008-03-20 19:41       ` Sam Ravnborg
2008-03-20 19:41         ` Sam Ravnborg
2008-03-20 19:50         ` [PATCH/RFC v4] introduce HAVE_UNALIGNED_ACCESS_SUPPORT " Johannes Berg
2008-03-20 19:50           ` Johannes Berg
2008-03-21  8:45           ` Ingo Molnar
2008-03-20 21:13     ` [PATCH/RFC v2] introduce ARCH_CAN_UNALIGNED_ACCESS " David Miller
2008-03-20 21:21       ` Johannes Berg
2008-03-20 21:21         ` Johannes Berg
2008-03-20 21:27         ` David Miller
2008-03-20 21:27           ` David Miller
2008-03-20 22:03         ` John W. Linville
2008-03-20 22:03           ` John W. Linville
2008-03-20 22:10           ` David Miller
2008-03-20 22:10             ` David Miller
2008-03-25 14:11       ` [PATCH/RFC v5] introduce HAVE_EFFICIENT_UNALIGNED_ACCESS " Johannes Berg
2008-04-02 10:24         ` Johannes Berg
2008-04-02 10:24           ` Johannes Berg

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=20080320181310.GA17884@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=dsd@gentoo.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@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.