From: Oleksandr Andrushchenko <andr2000@gmail.com>
To: Juergen Gross <jgross@suse.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xenproject.org, dmitry.torokhov@gmail.com,
jandryuk@gmail.com,
Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>,
linux-input@vger.kernel.org
Subject: Re: [PATCH v4 1/2] xen/kbdif: Add string constants for raw pointer
Date: Thu, 17 May 2018 08:29:57 +0300 [thread overview]
Message-ID: <66fe661f-8d1a-aefe-de50-02f37f756d94@gmail.com> (raw)
In-Reply-To: <2f77fa72-c0bd-7086-1197-23007ce91cb7@suse.com>
On 05/17/2018 07:28 AM, Juergen Gross wrote:
> On 16/05/18 06:59, Oleksandr Andrushchenko wrote:
>> On 05/11/2018 06:15 PM, Juergen Gross wrote:
>>> On 11/05/18 15:38, Konrad Rzeszutek Wilk wrote:
>>>> On Fri, May 11, 2018 at 09:37:57AM -0400, Konrad Rzeszutek Wilk wrote:
>>>>> On Wed, May 02, 2018 at 05:49:18PM +0300, Oleksandr Andrushchenko
>>>>> wrote:
>>>>>> From: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
>>>>>>
>>>>>> Add missing string constants for {feature|request}-raw-pointer
>>>>>> to align with the rest of the interface file.
>>>>>>
>>>>>> Fixes 7868654ff7fe ("kbdif: Define "feature-raw-pointer" and
>>>>>> "request-raw-pointer")
>>>>>>
>>>>>> Signed-off-by: Oleksandr Andrushchenko
>>>>>> <oleksandr_andrushchenko@epam.com>
>>>>> Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>>>> Juergen, you OK with an release-ack?
>>> Yes:
>>>
>>> Release-acked-by: Juergen Gross <jgross@suse.com>
>> Is this ack for both patches or this one only?
> It was meant for patch 1 only.
Clear
>> I see Konrad has applied this patch, but
>> "[Xen-devel][PATCH v4 2/2] xen/kbdif: Add features to disable keyboard
>> and pointer"
>> is still floating.
> In principle I'm fine with taking it for 4.11, but I think at this stage
> of the release there should be a formal request to include it.
...and the request should come from Konrad?
Or who else may request that?
And, as I have r-b's from Konrad for both patches,
will it be ok if we apply the corresponding changes to the
kernel now, so my change to xen-kbdfront is unblocked?
>
> Juergen
Thank you,
Oleksandr
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-05-17 5:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 14:49 [PATCH v4 1/2] xen/kbdif: Add string constants for raw pointer Oleksandr Andrushchenko
2018-05-02 14:49 ` [PATCH v4 2/2] xen/kbdif: Add features to disable keyboard and pointer Oleksandr Andrushchenko
2018-05-17 5:45 ` Oleksandr Andrushchenko
2018-05-17 5:50 ` Juergen Gross
2018-05-17 5:51 ` Oleksandr Andrushchenko
2018-05-17 14:09 ` Konrad Rzeszutek Wilk
2018-05-17 18:41 ` Oleksandr Andrushchenko
2018-05-08 5:41 ` [PATCH v4 1/2] xen/kbdif: Add string constants for raw pointer Oleksandr Andrushchenko
2018-05-11 13:37 ` Konrad Rzeszutek Wilk
2018-05-11 13:38 ` Konrad Rzeszutek Wilk
2018-05-11 15:15 ` Juergen Gross
2018-05-16 4:59 ` Oleksandr Andrushchenko
2018-05-17 4:28 ` Juergen Gross
2018-05-17 5:29 ` Oleksandr Andrushchenko [this message]
2018-05-17 5:42 ` Juergen Gross
2018-05-17 5:47 ` Oleksandr Andrushchenko
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=66fe661f-8d1a-aefe-de50-02f37f756d94@gmail.com \
--to=andr2000@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jandryuk@gmail.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-input@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).