From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Shane Wang <shane.wang@intel.com>
Cc: linux-kernel@vger.kernel.org, tboot-devel@lists.sourceforge.net,
jonmccune@cmu.edu, joseph.cihula@intel.com
Subject: Re: [PATCH] intel_txt: Add more explicit dependencies for CONFIG_INTEL_TXT
Date: Tue, 25 Jan 2011 13:39:17 +0800 [thread overview]
Message-ID: <20110125053917.GB13618@cr0.nay.redhat.com> (raw)
In-Reply-To: <1296067042-13485-1-git-send-email-shane.wang@intel.com>
On Thu, Jan 27, 2011 at 02:37:22AM +0800, Shane Wang wrote:
>This patch is to follow the recommended way in kconfig-language.txt to use HAVE_INTEL_TXT, so to add more explicit dependencies for CONFIG_INTEL_TXT.
>
>Signed-off-by: Jonathan McCune <jonmccune@cmu.edu>
>Signed-off-by: Shane Wang <shane.wang@intel.com>
>
Yes, this looks better.
Reviewed-by: WANG Cong <xiyou.wangcong@gmail.com>
prev parent reply other threads:[~2011-01-25 5:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 18:37 Shane Wang
2011-01-25 5:39 ` Américo Wang [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=20110125053917.GB13618@cr0.nay.redhat.com \
--to=xiyou.wangcong@gmail.com \
--cc=jonmccune@cmu.edu \
--cc=joseph.cihula@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shane.wang@intel.com \
--cc=tboot-devel@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®