All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Ren Qiaowei <qiaowei.ren@intel.com>
Cc: Joe Perches <joe@perches.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org,
	Gang Wei <gang.wei@intel.com>
Subject: Re: [PATCH] x86, tboot: provide debugfs interfaces to access TXT log
Date: Sun, 23 Jun 2013 21:33:12 -0700	[thread overview]
Message-ID: <51C7CC08.7080604@zytor.com> (raw)
In-Reply-To: <51C7B540.9020507@intel.com>

On 06/23/2013 07:56 PM, Ren Qiaowei wrote:
>>
> Well, I guess that I can use iomem related interface to fix these
> warnings caused by sparse.
> 

And you SHOULD.  Passing around pointers to I/O space without even
annotating them isn't really very clean.

	-hpa



      reply	other threads:[~2013-06-24  4:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-23  7:54 [PATCH] x86, tboot: provide debugfs interfaces to access TXT log Qiaowei Ren
2013-06-23  8:36 ` Joe Perches
2013-06-24  2:56   ` Ren Qiaowei
2013-06-24  4:33     ` H. Peter Anvin [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=51C7CC08.7080604@zytor.com \
    --to=hpa@zytor.com \
    --cc=gang.wei@intel.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=qiaowei.ren@intel.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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.