linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Roland McGrath <roland@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [PATCH] x86 user_regset_view table fix for ia32 on 64-bit
Date: Tue, 13 May 2008 14:28:59 +0200	[thread overview]
Message-ID: <20080513122859.GC14973@elte.hu> (raw)
In-Reply-To: <20080509224344.152FD26FA85@magilla.localdomain>


* Roland McGrath <roland@redhat.com> wrote:

> The user_regset_view table for the 32-bit regsets on the 64-bit build 
> had the wrong sizes for the FP regsets.  This bug had no user-visible 
> effect (just on kernel modules using the user_regset interfaces and 
> the like). But the fix is trivial and risk-free.

applied, thanks Roland.

	Ingo

      reply	other threads:[~2008-05-13 12:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-09 22:43 [PATCH] x86 user_regset_view table fix for ia32 on 64-bit Roland McGrath
2008-05-13 12:28 ` Ingo Molnar [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=20080513122859.GC14973@elte.hu \
    --to=mingo@elte.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roland@redhat.com \
    --cc=stable@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).