From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Jan Beulich" <JBeulich@suse.com>
Cc: <mingo@elte.hu>, <tglx@linutronix.de>, <hpa@zytor.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH, resend] x86: constify PCI raw ops structures
Date: Fri, 14 Oct 2011 09:06:46 -0700 [thread overview]
Message-ID: <20111014090646.06aef304@jbarnes-desktop> (raw)
In-Reply-To: <4E71CC5B020000780005636B@nat28.tlf.novell.com>
[-- Attachment #1: Type: text/plain, Size: 486 bytes --]
On Thu, 15 Sep 2011 08:58:51 +0100
"Jan Beulich" <JBeulich@suse.com> wrote:
> As with any other such change, the goal is to prevent inadvertent
> writes to these structures (assuming DEBUG_RODATA is enabled), and to
> separate data (possibly frequently) written to from such never getting
> modified.
>
> Signed-off-by: Jan Beulich <jbeulich@novell.com>
Yay finally got this one applied to linux-next, thanks Jan!
--
Jesse Barnes, Intel Open Source Technology Center
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2011-10-14 16:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 7:58 Jan Beulich
2011-10-14 16:06 ` Jesse Barnes [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=20111014090646.06aef304@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=JBeulich@suse.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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
all inboxes | Powered by JetHome®