From: Ingo Molnar <mingo@kernel.org>
To: Cliff Wickman <cpw@sgi.com>
Cc: linux-kernel@vger.kernel.org, alex.shi@intel.com,
jbeulich@suse.com, tglx@linutronix.de, hpa@zytor.com
Subject: Re: [alex.shi@intel.com: Re: [PATCH] UV: fix incorrect tlb flush all issue]
Date: Fri, 14 Sep 2012 07:56:51 +0200 [thread overview]
Message-ID: <20120914055651.GE9043@gmail.com> (raw)
In-Reply-To: <20120913212003.GA16789@sgi.com>
* Cliff Wickman <cpw@sgi.com> wrote:
> On Thu, Sep 13, 2012 at 05:53:10PM +0200, Ingo Molnar wrote:
> >
> > Ack?
> >
> > Thanks,
> >
> > Ingo
>
> Ack.
> But with the adjustment below. The 'end' argument was not declared long.
Ok, great - mind sending the updated patch properly under a new
title (the old one doesn't seem ideal), with an expanded
changelog and with a Signed-off-by: Cliff Wickman, instead of
the Acked-by?
Thanks,
Ingo
prev parent reply other threads:[~2012-09-14 5:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120913155310.GA4081@gmail.com>
2012-09-13 21:20 ` [alex.shi@intel.com: Re: [PATCH] UV: fix incorrect tlb flush all issue] Cliff Wickman
2012-09-14 0:24 ` Alex Shi
2012-09-14 5: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=20120914055651.GE9043@gmail.com \
--to=mingo@kernel.org \
--cc=alex.shi@intel.com \
--cc=cpw@sgi.com \
--cc=hpa@zytor.com \
--cc=jbeulich@suse.com \
--cc=linux-kernel@vger.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