Re: [PATCH v3] Input: sparse-keymap - use a managed allocation for keymap copy

From	Dmitry Torokhov <dmitry.torokhov@gmail.com>
Newsgroups	linux.kernel
Subject	Re: [PATCH v3] Input: sparse-keymap - use a managed allocation for keymap copy
Date	2017-03-09 19:10 +0100
Message-ID	<tjaFI-ma-19@gated-at.bofh.it> (permalink)
References	(1 earlier) <tiOlP-1Pw-7@gated-at.bofh.it> <tiR0n-3EK-47@gated-at.bofh.it> <tiR0n-3EK-45@gated-at.bofh.it> <tiSIN-4D8-3@gated-at.bofh.it> <tj1j5-2og-51@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

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

Thread

[PATCH v3] Input: sparse-keymap - use a managed allocation for keymap copy Michał Kępień <kernel@kempniu.pl> - 2017-03-08 09:30 +0100
  Re: [PATCH v3] Input: sparse-keymap - use a managed allocation for  keymap copy Dmitry Torokhov <dmitry.torokhov@gmail.com> - 2017-03-08 19:20 +0100
    Re: [PATCH v3] Input: sparse-keymap - use a managed allocation for  keymap copy Dmitry Torokhov <dmitry.torokhov@gmail.com> - 2017-03-08 22:10 +0100
      Re: [PATCH v3] Input: sparse-keymap - use a managed allocation for  keymap copy Andy Shevchenko <andy.shevchenko@gmail.com> - 2017-03-09 00:00 +0100
        Re: [PATCH v3] Input: sparse-keymap - use a managed allocation for  keymap copy Michał Kępień <kernel@kempniu.pl> - 2017-03-09 09:10 +0100
          Re: [PATCH v3] Input: sparse-keymap - use a managed allocation for  keymap copy Dmitry Torokhov <dmitry.torokhov@gmail.com> - 2017-03-09 19:10 +0100
    Re: [PATCH v3] Input: sparse-keymap - use a managed allocation for  keymap copy Andy Shevchenko <andy.shevchenko@gmail.com> - 2017-03-08 22:10 +0100

csiph-web