From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Oleksandr Andrushchenko <andr2000@gmail.com>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
xen-devel@lists.xenproject.org, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org, jgross@suse.com, lyan@suse.com,
andrii_chepurnyi@epam.com,
Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Subject: Re: [PATCH v3 2/2] Input: xen-kbdfront - allow better run-time configuration
Date: Thu, 17 May 2018 10:29:05 -0400 [thread overview]
Message-ID: <20180517142905.GF12679@char.us.oracle.com> (raw)
In-Reply-To: <60ed5392-eff6-be1c-f092-bb93184db060@gmail.com>
On Thu, May 17, 2018 at 04:09:04PM +0300, Oleksandr Andrushchenko wrote:
> On 05/17/2018 04:08 PM, Boris Ostrovsky wrote:
> > On 05/17/2018 01:31 AM, Oleksandr Andrushchenko wrote:
> > > I will go with the change you suggested and
> > > I'll send v4 tomorrow then.
> >
> >
> > Please make sure your changes to kbdif.h are in Xen first. I believe you
> > submitted a patch there but I don't see it in the staging tree yet.
> Sure, I already have Release ack for the one which is not
> in Xen tree yet, hope Konrad can apply it today,
> so tomorrow Xen and Linux are both ok (or by the time
It is checked in (on the Xen tree).
> I send v4).
> > -boris
> Thank you,
> Oleksandr
prev parent reply other threads:[~2018-05-17 14:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 14:40 [PATCH v3 1/2] xen/kbdif: Sync up with the canonical definition in Xen Oleksandr Andrushchenko
2018-05-14 14:40 ` [PATCH v3 2/2] Input: xen-kbdfront - allow better run-time configuration Oleksandr Andrushchenko
2018-05-16 17:15 ` Dmitry Torokhov
2018-05-16 17:47 ` Oleksandr Andrushchenko
2018-05-16 21:08 ` Dmitry Torokhov
2018-05-17 5:31 ` Oleksandr Andrushchenko
2018-05-17 13:08 ` Boris Ostrovsky
2018-05-17 13:09 ` Oleksandr Andrushchenko
2018-05-17 14:29 ` Konrad Rzeszutek Wilk [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=20180517142905.GF12679@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=andr2000@gmail.com \
--cc=andrii_chepurnyi@epam.com \
--cc=boris.ostrovsky@oracle.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jgross@suse.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lyan@suse.com \
--cc=oleksandr_andrushchenko@epam.com \
--cc=xen-devel@lists.xenproject.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