From: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
George Dunlap <george.dunlap@eu.citrix.com>
Cc: "Lendacky, Thomas" <Thomas.Lendacky@amd.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
"shurd@broadcom.com" <shurd@broadcom.com>,
"Suthikulpanit, Suravee" <Suravee.Suthikulpanit@amd.com>,
"Hurwitz, Sherry" <sherry.hurwitz@amd.com>
Subject: Re: [PATCH V8] ns16550: Add support for UART present in Broadcom TruManage capable NetXtreme chips
Date: Mon, 24 Feb 2014 10:12:22 -0600 [thread overview]
Message-ID: <530B6F66.8070201@amd.com> (raw)
In-Reply-To: <52AF0E35.7070000@citrix.com>
On 12/16/2013 8:29 AM, Andrew Cooper wrote:
>
> It turns out that we have some of this hardware in our testing pool.
>
> Therefore,
>
> Tested-by: Andrew Cooper <andrew.cooper3@citrix.com> (by way of backport
> to 4.3)
>
> I would however agree that on the whole, it is probably too high-risk /
> low-reward for inclusion in 4.4, but it should be fine for accepting as
> soon as the 4.5 window opens.
>
>
Ping..
Jan (or George), could you please clarify if (hopefully) there are no
other concerns regarding the patch, it would be picked up automatically
for 4.5?
Thanks,
-Aravind.
next prev parent reply other threads:[~2014-02-24 16:12 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 [this message]
2014-02-24 16:26 ` Jan Beulich
2014-02-24 18:08 ` Aravind Gopalakrishnan
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=530B6F66.8070201@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).