From: David Miller <davem@davemloft.net>
To: horms@verge.net.au
Cc: luming.yu@gmail.com, linux-ia64@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix typo in per_cpu_offset
Date: Tue, 30 Oct 2007 07:36:22 +0000 [thread overview]
Message-ID: <20071030.003622.265888160.davem@davemloft.net> (raw)
In-Reply-To: <20071030071513.GE5361@verge.net.au>
From: Simon Horman <horms@verge.net.au>
Date: Tue, 30 Oct 2007 16:15:13 +0900
> Though curiuously with my config nothing uses per_cpu_offset()
> (I added a bogus call to produce an error.) Is it actually
> used on ia64?
It is unused, and in that regard should probably be deleted.
include/asm-generic/percpu.h defines a seemingly similarly
unused per_cpu_offset() macro define as well
next prev parent reply other threads:[~2007-10-30 7:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 7:15 [PATCH] fix typo in per_cpu_offset Luming Yu
2007-10-30 7:15 ` Simon Horman
2007-10-30 7:36 ` David Miller [this message]
2007-10-30 8:50 ` Simon Horman
2007-11-07 6:44 ` Simon Horman
2007-11-07 6:50 ` Luming Yu
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=20071030.003622.265888160.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=horms@verge.net.au \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luming.yu@gmail.com \
/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