From: Borislav Petkov <bp@suse.de>
To: B_B_Singh@DELL.com
Cc: stuart.w.hayes@gmail.com, hpa@zytor.com, tglx@linutronix.de,
mingo@redhat.com, x86@kernel.org, linux-kernel@vger.kernel.org,
matt.fleming@intel.com, Jiri Kosina <jkosina@suse.cz>
Subject: Re: [PATCH] x86: Configure NX support earlier in setup_arch
Date: Thu, 13 Nov 2014 13:30:45 +0100 [thread overview]
Message-ID: <20141113123045.GA14421@pd.tnic> (raw)
In-Reply-To: <8B2F6FFD0BD1E448853114367400A3730702007068@BLRX7MCDC203.AMER.DELL.COM>
On Thu, Nov 13, 2014 at 12:09:02PM +0530, B_B_Singh@DELL.com wrote:
> I feel this can be a valid scenario where user wants to disable the
> memory protection (NX flag disable) for his requirement, in that case he
> will hit this issue. So request you to please revisit this patch.
First of all, please do not top-post. Here's why:
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
Revisit this patch how? I'm not sure I understand...
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2014-11-13 12:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 1:47 [PATCH] x86: Configure NX support earlier in setup_arch Stuart Hayes
2014-07-08 22:34 ` Stuart Hayes
2014-07-08 22:38 ` H. Peter Anvin
2014-07-10 0:56 ` Stuart Hayes
2014-07-14 17:22 ` Borislav Petkov
2014-07-14 17:28 ` H. Peter Anvin
2014-07-14 17:35 ` Borislav Petkov
2014-11-13 6:39 ` B_B_Singh
2014-11-13 12:30 ` Borislav Petkov [this message]
2014-11-13 13:40 ` B_B_Singh
2014-11-13 15:48 ` Thomas Gleixner
2014-11-13 12:54 ` Thomas Gleixner
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=20141113123045.GA14421@pd.tnic \
--to=bp@suse.de \
--cc=B_B_Singh@DELL.com \
--cc=hpa@zytor.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mingo@redhat.com \
--cc=stuart.w.hayes@gmail.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.