From: "H. Peter Anvin" <hpa@zytor.com>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org,
Intel Linux Wireless <ilw@linux.intel.com>,
linux-scsi@vger.kernel.org, x86@kernel.org,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH 0/9] strict user copy checks on x86_64
Date: Tue, 24 May 2011 16:33:33 -0700 [thread overview]
Message-ID: <4DDC404D.8030505@zytor.com> (raw)
In-Reply-To: <4DDC232F.7080005@codeaurora.org>
On 05/24/2011 02:29 PM, Stephen Boyd wrote:
>
> It looks like 1, 2, 4, 6, and 7 got picked up. Should I resend the left
> over patches with appropriate acked-bys and tags? Would it be
> appropriate to push this through your tree?
>
I was first going to think I'd pick up 8 and 9 in tip, but since 9 is
cross-architecture, Andrew's tree might be better.
Acked-by: H. Peter Anvin <hpa@zytor.com>
-hpa
prev parent reply other threads:[~2011-05-24 23:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 23:50 [PATCH 0/9] strict user copy checks on x86_64 Stephen Boyd
2011-05-12 23:50 ` [PATCH 1/9] iwlegacy: Silence DEBUG_STRICT_USER_COPY_CHECKS=y warning Stephen Boyd
2011-05-13 0:01 ` wwguy
2011-05-13 9:08 ` Stanislaw Gruszka
2011-05-12 23:50 ` [PATCH 2/9] iwlwifi: " Stephen Boyd
2011-05-13 0:02 ` wwguy
2011-05-12 23:50 ` [PATCH 3/9] [SCSI] lpfc: " Stephen Boyd
2011-05-24 13:32 ` James Smart
2011-05-12 23:50 ` [PATCH 4/9] debugfs: " Stephen Boyd
2011-05-13 23:14 ` Greg KH
2011-05-12 23:50 ` [PATCH 5/9] kprobes: " Stephen Boyd
2011-05-13 0:29 ` Masami Hiramatsu
2011-05-12 23:50 ` [PATCH 6/9] Bluetooth: " Stephen Boyd
2011-05-13 21:06 ` Gustavo F. Padovan
2011-05-13 21:06 ` Gustavo F. Padovan
2011-05-12 23:50 ` [PATCH 7/9] ASoC: " Stephen Boyd
2011-05-16 16:26 ` Liam Girdwood
2011-05-16 16:26 ` Liam Girdwood
2011-05-16 20:22 ` Mark Brown
2011-05-16 20:22 ` Mark Brown
2011-05-12 23:50 ` [PATCH 8/9] x86: Implement strict user copy checks for x86_64 Stephen Boyd
2011-05-13 10:15 ` Ingo Molnar
2011-05-12 23:50 ` [PATCH 9/9] Consolidate CONFIG_DEBUG_STRICT_USER_COPY_CHECKS Stephen Boyd
2011-05-13 0:55 ` Chris Metcalf
2011-05-13 0:55 ` Chris Metcalf
2011-05-13 7:31 ` Ingo Molnar
2011-05-13 16:55 ` Arnd Bergmann
2011-05-24 21:29 ` [PATCH 0/9] strict user copy checks on x86_64 Stephen Boyd
2011-05-24 23:33 ` H. Peter Anvin [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=4DDC404D.8030505@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=ilw@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=sboyd@codeaurora.org \
--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 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.