From: Arjan van de Ven <arjan@linux.intel.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Patch 2 of 8] annotate the PDA structure with offsets
Date: Sat, 18 Mar 2006 10:46:33 +0100 [thread overview]
Message-ID: <441BD6F9.8050003@linux.intel.com> (raw)
In-Reply-To: <20060318093853.GA28846@elte.hu>
Ingo Molnar wrote:
> * Arjan van de Ven <arjan@linux.intel.com> wrote:
>
>> Change the comments in the pda structure to make the first fields to
>> have their offset documented (the rest of the fields follows in a
>> later patch) and to have the comments aligned
>
> i think offset 40 should be build-time checked - then you dont have to
> do this annotation.
>
ok good idea; I'll investigate
next prev parent reply other threads:[~2006-03-18 9:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-17 16:10 [Patch 0/8] Port of -fstack-protector to the kernel Arjan van de Ven
2006-03-17 16:11 ` [Patch 1 of 8] Pack the x86-64 PDA structure Arjan van de Ven
2006-03-17 16:13 ` [Patch 3 of 8] Introduce a config option for stack-protector Arjan van de Ven
2006-03-17 16:13 ` [Patch 2 of 8] annotate the PDA structure with offsets Arjan van de Ven
2006-03-18 9:38 ` Ingo Molnar
2006-03-18 9:46 ` Arjan van de Ven [this message]
2006-03-17 16:14 ` [Patch 4 of 8] Add the cookie field Arjan van de Ven
2006-03-17 16:14 ` [Patch 5 of 8] Add the __stack_chk_fail() function Arjan van de Ven
2006-03-19 17:57 ` Nix
2006-03-19 18:06 ` Arjan van de Ven
2006-03-19 19:06 ` Nix
2006-03-17 16:15 ` [Patch 6 of 8] Implement the CFLAGs side Arjan van de Ven
2006-03-17 16:16 ` [Patch 7 of 8] Finish PDA offset annotations Arjan van de Ven
2006-03-17 16:17 ` [Patch 8 of 8] GCC 4.1 patch for kernel stack-protector Arjan van de Ven
2006-03-17 16:50 ` [Patch 0/8] Port of -fstack-protector to the kernel Michal Piotrowski
2006-03-17 16:53 ` Arjan van de Ven
2006-03-18 9:41 ` Ingo Molnar
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=441BD6F9.8050003@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.