From: Ingo Molnar <mingo@elte.hu>
To: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: hpa@zytor.com, tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [patch 3/3] x86, xsave: use BUG_ON() instead of BUILD_BUG_ON()
Date: Thu, 14 Aug 2008 10:56:47 +0200 [thread overview]
Message-ID: <20080814085647.GE1650@elte.hu> (raw)
In-Reply-To: <20080813183857.246823000@linux-os.sc.intel.com>
* Suresh Siddha <suresh.b.siddha@intel.com> wrote:
> All these structure sizes are runtime determined. So use a runtime bug
> check.
applied these patches to tip/x86/xsave:
f65bc21: x86, xsave: use BUG_ON() instead of BUILD_BUG_ON()
ed40595: x86, xsave: clear the user buffer before doing fxsave/xsave
ee2b92a: x86, xsave: remove the redundant access_ok() in setup_rt_frame()
thanks Suresh.
Ingo
prev parent reply other threads:[~2008-08-14 8:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 18:38 [patch 1/3] x86, xsave: remove the redundant access_ok() in setup_rt_frame() Suresh Siddha
2008-08-13 18:38 ` [patch 2/3] x86, xsave: clear the user buffer before doing fxsave/xsave Suresh Siddha
2008-08-13 18:38 ` [patch 3/3] x86, xsave: use BUG_ON() instead of BUILD_BUG_ON() Suresh Siddha
2008-08-14 8:56 ` 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=20080814085647.GE1650@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=suresh.b.siddha@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox