From: Greg KH <gregkh@linuxfoundation.org>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: xen-devel@lists.xensource.com,
David Vrabel <david.vrabel@citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Dave Scott <Dave.Scott@eu.citrix.com>,
linux-kernel@vger.kernel.org, jslaby@suse.cz
Subject: Re: [PATCH] xen_hvc: no reason to write the type key on xenstore
Date: Tue, 12 Aug 2014 10:51:32 +0800 [thread overview]
Message-ID: <20140812025132.GG17509@kroah.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1408111532020.2293@kaball.uk.xensource.com>
On Mon, Aug 11, 2014 at 03:32:48PM +0100, Stefano Stabellini wrote:
> CC'ing tty maintainers.
Why? Is that how you submit a patch to be included to the kernel tree?
(hint, the answer is no, and also you should cc: the linux-serial
list...)
greg k-h
next prev parent reply other threads:[~2014-08-12 2:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-11 11:54 [PATCH] xen_hvc: no reason to write the type key on xenstore Stefano Stabellini
2014-08-11 11:58 ` David Vrabel
2014-08-11 14:32 ` Stefano Stabellini
2014-08-12 2:51 ` Greg KH [this message]
2014-08-12 9:06 ` Stefano Stabellini
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=20140812025132.GG17509@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Dave.Scott@eu.citrix.com \
--cc=david.vrabel@citrix.com \
--cc=jslaby@suse.cz \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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