From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: "Michał Kępień" <kernel@kempniu.pl>,
linux-input <linux-input@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Platform Driver" <platform-driver-x86@vger.kernel.org>,
"Andy Shevchenko" <andy@infradead.org>
Subject: Re: [PATCH v3] Input: sparse-keymap - use a managed allocation for keymap copy
Date: Wed, 8 Mar 2017 23:47:26 +0200 [thread overview]
Message-ID: <CAHp75VdKNnnyu5cJr=uzvimfbwJJyZ+nwBkJzUxu+RitHf1_1Q@mail.gmail.com> (raw)
In-Reply-To: <20170308210506.GD20567@dtor-ws>
On Wed, Mar 8, 2017 at 11:05 PM, Dmitry Torokhov
<dmitry.torokhov@gmail.com> wrote:
> On Wed, Mar 08, 2017 at 10:50:16PM +0200, Andy Shevchenko wrote:
>> On Wed, Mar 8, 2017 at 8:12 PM, Dmitry Torokhov
>> <dmitry.torokhov@gmail.com> wrote:
>> > On Wed, Mar 08, 2017 at 09:22:17AM +0100, Michał Kępień wrote:
>> If there PDx86 related patches are anticipated this cycle, definitely
>> we need an immutable branch (perhaps based on v4.11-rc1).
>
> OK, I'll make one (based on 4.10 final - the patch should apply cleanly
> there and there is no point of forcing anyone's workflow to use kernel
> in the beginning of stabilization cycle).
Fine by me.
> As to whether there are PDx86 patches - I hope Michał will supply them
> ;)
Michał, whenever you send the first one based on this change, please
mention that it has dependency, I will pull the immutable branch at
that time.
Thanks.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2017-03-08 21:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 8:22 [PATCH v3] Input: sparse-keymap - use a managed allocation for keymap copy Michał Kępień
2017-03-08 18:12 ` Dmitry Torokhov
2017-03-08 20:50 ` Andy Shevchenko
2017-03-08 21:05 ` Dmitry Torokhov
2017-03-08 21:47 ` Andy Shevchenko [this message]
2017-03-09 7:58 ` Michał Kępień
2017-03-09 18:08 ` Dmitry Torokhov
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='CAHp75VdKNnnyu5cJr=uzvimfbwJJyZ+nwBkJzUxu+RitHf1_1Q@mail.gmail.com' \
--to=andy.shevchenko@gmail.com \
--cc=andy@infradead.org \
--cc=dmitry.torokhov@gmail.com \
--cc=kernel@kempniu.pl \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.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).