From: Tejun Heo <tj@kernel.org>
To: Dave Young <dyoung@redhat.com>
Cc: xiyou.wangcong@gmail.com, kexec@lists.infradead.org,
tim@edgecast.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] percpu: add comment to per_cpu_ptr_to_phys
Date: Wed, 23 Nov 2011 08:22:54 -0800 [thread overview]
Message-ID: <20111123162254.GD25780@google.com> (raw)
In-Reply-To: <20111123084543.GA2923@darkstar.nay.redhat.com>
Hello,
On Wed, Nov 23, 2011 at 04:45:43PM +0800, Dave Young wrote:
> add comments about current per_cpu_ptr_to_phys implementation
> to explain why the logic is more complicated than necessary.
>
> Signed-off-by: Dave Young <dyoung@redhat.com>
Moved the comment into the kerneldoc comment and applied to
percpu/for-3.2-fixes.
Thank you very much.
--
tejun
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2011-11-23 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 8:45 [PATCH] percpu: add comment to per_cpu_ptr_to_phys Dave Young
2011-11-23 16:22 ` Tejun Heo [this message]
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=20111123162254.GD25780@google.com \
--to=tj@kernel.org \
--cc=dyoung@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tim@edgecast.com \
--cc=xiyou.wangcong@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