From: Andreas Schwab <schwab@linux-m68k.org>
To: Igor Zhbanov <izh1979@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Why get/put_unaligned are hidden behind #ifdef __KERNEL__ on PowerPC and Microblaze?
Date: Sun, 31 Oct 2010 16:27:22 +0100 [thread overview]
Message-ID: <m2bp6apelh.fsf@igel.home> (raw)
In-Reply-To: <AANLkTimtfUXN9oTQ=BaxNz+h+mgwFBPrzN_Nggbai+ZJ@mail.gmail.com> (Igor Zhbanov's message of "Sun, 31 Oct 2010 18:13:31 +0300")
Igor Zhbanov <izh1979@gmail.com> writes:
> I have found that functions get_unaligned and put_unaligned from unaligned.h
> are hidden behind #ifdef __KERNEL__ on PowerPC and Microblaze architectures.
> And are not hidden on other platforms. But why?
Since <asm/unaligned.h> is not an exported header the point is moot.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2010-10-31 15:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-31 15:13 Why get/put_unaligned are hidden behind #ifdef __KERNEL__ on PowerPC and Microblaze? Igor Zhbanov
2010-10-31 15:27 ` Andreas Schwab [this message]
2010-10-31 16:10 ` Igor Zhbanov
2010-10-31 17:45 ` Arnd Bergmann
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=m2bp6apelh.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=izh1979@gmail.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox