From: Kees Cook <kees.cook@canonical.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH 1/2] x86: give names to realmode wakeup flags
Date: Tue, 5 Jul 2011 18:27:39 -0700 [thread overview]
Message-ID: <20110706012739.GA32221@outflux.net> (raw)
In-Reply-To: <4E1392BA.8010708@zytor.com>
On Tue, Jul 05, 2011 at 03:39:54PM -0700, H. Peter Anvin wrote:
> On 07/04/2011 03:35 PM, Kees Cook wrote:
> > Instead of using literals, use a common set of names for the
> > user-controlled realmode wakeup flags.
> >
> > Signed-off-by: Kees Cook <kees.cook@canonical.com>
>
> I'm sorry, but I really have to complain about this:
>
> This was a very unfriendly thing to do.
Obviously I wasn't trying to be unfriendly. :P
> You took a patch that is a bug fix to be considered for -stable,
> and you applied it *on top of a cleanup patch*.
It wasn't clear to me if the MISC_ENABLE reload should be considered for
stable (it does technically "more" than my original patch, and changes
the resume header structure, etc). If it should be forwarded to -stable,
that's fine too. I just didn't want to presume.
> They should not have been part of the same patchset,
> but *certainly* not in that order.
Since they hit the same .h file in the same location, I wasn't sure what
order to do it in. It seemed unhelpful to send them separately.
> Please resubmit.
Sure thing -- in the opposite order, or totally separate from each other?
-Kees
--
Kees Cook
Ubuntu Security Team
next prev parent reply other threads:[~2011-07-06 1:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 22:35 [PATCH 0/2] x86: restore MISC_ENABLE MSR in realmode wakeup Kees Cook
2011-07-04 22:35 ` [PATCH 1/2] x86: give names to realmode wakeup flags Kees Cook
2011-07-05 22:39 ` H. Peter Anvin
2011-07-06 1:27 ` Kees Cook [this message]
2011-07-06 2:41 ` H. Peter Anvin
2011-07-04 22:35 ` [PATCH 2/2] x86: restore MISC_ENABLE MSR in realmode wakeup Kees Cook
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=20110706012739.GA32221@outflux.net \
--to=kees.cook@canonical.com \
--cc=hpa@zytor.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
--cc=x86@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®