All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Harvey Harrison <harvey.harrison@gmail.com>,
	Ingo Molnar <mingo@elte.hu>, Roland McGrath <roland@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/9] x86: change most X86_32 pt_regs members to unsigned long
Date: Fri, 08 Feb 2008 13:17:38 -0800	[thread overview]
Message-ID: <47ACC6F2.8050601@zytor.com> (raw)
In-Reply-To: <20080208211344.GB15571@martell.zuzino.mipt.ru>

Alexey Dobriyan wrote:
> Why?! You don't have even minimal chances to unify pt_regs for i386 and
> x86_64.

The structure itself, no.  Some of the users may very well be candidates 
for unification, however.

	-hpa

  reply	other threads:[~2008-02-08 21:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-08 20:09 [PATCH 1/9] x86: change most X86_32 pt_regs members to unsigned long Harvey Harrison
2008-02-08 21:13 ` Alexey Dobriyan
2008-02-08 21:17   ` H. Peter Anvin [this message]
2008-02-17 14:00 ` 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=47ACC6F2.8050601@zytor.com \
    --to=hpa@zytor.com \
    --cc=adobriyan@gmail.com \
    --cc=harvey.harrison@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=roland@redhat.com \
    --cc=tglx@linutronix.de \
    /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.