From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Michał Kępień" <kernel@kempniu.pl>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
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: Thu, 9 Mar 2017 10:08:14 -0800 [thread overview]
Message-ID: <20170309180814.GE20077@dtor-ws> (raw)
In-Reply-To: <20170309075854.GA1620@ozzy.nask.waw.pl>
On Thu, Mar 09, 2017 at 08:58:54AM +0100, Michał Kępień wrote:
> > 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.
>
> Noted. I will prepare the patches and submit them within the next few
> days.
OK, the branch with this single commit applied to 4.10 is
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git ib/4.10-sparse-keymap-managed
Thanks.
--
Dmitry
prev parent reply other threads:[~2017-03-09 18:08 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
2017-03-09 7:58 ` Michał Kępień
2017-03-09 18:08 ` Dmitry Torokhov [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=20170309180814.GE20077@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.