mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: Alexander Kuleshov <alex0xax@gmail.com>
Cc: keescook@chromium.org, yinghai@kernel.org, hpa@zytor.com,
	mingo@redhat.com, bp@suse.de, matt.fleming@intel.com,
	vgoyal@redhat.com, tglx@linutronix.de,
	linux-kernel@vger.kernel.org
Subject: Re: [Patch v3 3/7] x86, kaslr: Add two functions which will be used later
Date: Mon, 9 Mar 2015 20:40:13 +0800	[thread overview]
Message-ID: <20150309124013.GA1741@dhcp-17-102.nay.redhat.com> (raw)
In-Reply-To: <CAFkLPWHsQg5vUFxXDL_OFOOtGzcZTbVPzPSfPtntDnsyuCgvKA@mail.gmail.com>

On 03/08/15 at 07:58pm, Alexander Kuleshov wrote:
> Hello,
> 
> May be necessary to add comments that they will be used later, to
> prevent patches like 'removed unused......'

Hi, 

Thanks for your comment. Do you mean adding comment above function
definition, later remove the comment when call it?

Thanks
Baoquan

  reply	other threads:[~2015-03-09 12:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-08  5:38 [Patch v3 0/7] randomize kernel physical address and virtual address separately Baoquan He
2015-03-08  5:38 ` [Patch v3 1/7] x86, kaslr: Fix a bug that relocation can not be handled when kernel is loaded above 2G Baoquan He
2015-03-08  5:38 ` [Patch v3 2/7] x86, kaslr: Introduce struct slot_area to manage randomization slot info Baoquan He
2015-03-08  5:38 ` [Patch v3 3/7] x86, kaslr: Add two functions which will be used later Baoquan He
2015-03-08 13:58   ` Alexander Kuleshov
2015-03-09 12:40     ` Baoquan He [this message]
2015-03-08  5:38 ` [Patch v3 4/7] x86, kaslr: Introduce fetch_random_virt_offset to randomize the kernel text mapping address Baoquan He
2015-03-08  5:38 ` [Patch v3 5/7] x86, kaslr: Randomize physical and virtual address of kernel separately Baoquan He
2015-03-08  5:38 ` [Patch v3 6/7] x86, kaslr: Add support of kernel physical address randomization above 4G Baoquan He
2015-03-08  5:38 ` [Patch v3 7/7] x86, kaslr: Remove useless codes Baoquan He

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=20150309124013.GA1741@dhcp-17-102.nay.redhat.com \
    --to=bhe@redhat.com \
    --cc=alex0xax@gmail.com \
    --cc=bp@suse.de \
    --cc=hpa@zytor.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt.fleming@intel.com \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=vgoyal@redhat.com \
    --cc=yinghai@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 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®