xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Thomas Lendacky <Thomas.Lendacky@amd.com>,
	George Dunlap <george.dunlap@eu.citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>,
	Sherry Hurwitz <sherry.hurwitz@amd.com>,
	"shurd@broadcom.com" <shurd@broadcom.com>
Subject: Re: [PATCH V8] ns16550: Add support for UART present in Broadcom TruManage capable NetXtreme chips
Date: Mon, 24 Feb 2014 12:08:25 -0600	[thread overview]
Message-ID: <530B8A99.8030909@amd.com> (raw)
In-Reply-To: <530B80C5020000780011EEBE@nat28.tlf.novell.com>

On 2/24/2014 10:26 AM, Jan Beulich wrote:
>>>   
>>> It's been well over two months since you posted this, and it's still not
>>> having Keir's ack. The best way therefore is for you to re-post, with
>>> Keir properly Cc-ed, and with Andrew's Tested-by added.
>>>
>>> Jan
>>>
>>>

Ok, will do..

Shall I retain the version number or start from scratch?

-Aravind.

  reply	other threads:[~2014-02-24 18:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-05 22:38 [PATCH V8] ns16550: Add support for UART present in Broadcom TruManage capable NetXtreme chips Aravind Gopalakrishnan
2013-12-06  8:41 ` Jan Beulich
2013-12-06 15:52   ` Aravind Gopalakrishnan
2013-12-06 16:00     ` George Dunlap
2013-12-06 20:31       ` Aravind Gopalakrishnan
2013-12-09  8:22         ` Jan Beulich
2013-12-16 14:29           ` Andrew Cooper
2014-02-24 16:12             ` Aravind Gopalakrishnan
2014-02-24 16:26               ` Jan Beulich
2014-02-24 18:08                 ` Aravind Gopalakrishnan [this message]
2014-02-25  7:53                   ` Jan Beulich

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=530B8A99.8030909@amd.com \
    --to=aravind.gopalakrishnan@amd.com \
    --cc=JBeulich@suse.com \
    --cc=Suravee.Suthikulpanit@amd.com \
    --cc=Thomas.Lendacky@amd.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=sherry.hurwitz@amd.com \
    --cc=shurd@broadcom.com \
    --cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).