----- Original Message -----
> From: "Dmitry Torokhov" <[email protected]>
> To: "CAI Qian" <[email protected]>
> Cc: [email protected], [email protected], [email protected]
> Sent: Wednesday, December 5, 2012 2:53:43 AM
> Subject: Re: [PATCH] Input: mousedev - move /dev/input/mice to the correct 
> minor
> 
> On Tue, Dec 04, 2012 at 04:44:18AM -0500, CAI Qian wrote:
> > When doing conversion to dynamic input numbers I inadvertently
> > moved
> > /dev/input/mice from c,13,63 to c,13,31. We need to fix this so
> > that
> > setups with statically populated /dev continue working.
> > 
> > Tested-by: Krzysztof Mazur <[email protected]>
> > Tested-by: Pavel Machek <[email protected]>
> > Signed-off-by: Dmitry Torokhov <[email protected]>
> > 
> > Upstream-ID: c91cb7a75eaf65358aac5ea2b512ac60a9437ff4
> > Stable-trees: 3.0.x, 3.4.x, 3.6.x
> > Signed-off-by: CAI Qian <[email protected]>
> 
> NAK. The offending change (7f8d4cad1e4e11a45d02bd6e024cc2812963c38a)
> went into 3.7-rc4 and therefore does not need to be present in
> stable.
> 
> You haven't tested the change, have you?
I have checked, and this patch was applied and compiled cleanly for
those stable trees. If only the offending change commit ID was
mentioned in the patch changelog in the first place, I would be
able to figure out that was not applicable for stable trees. Please
ignore it then.

CAI Qian
> 
> > 
> > diff --git a/drivers/input/mousedev.c b/drivers/input/mousedev.c
> > index 8f02e3d..4c842c3 100644
> > --- a/drivers/input/mousedev.c
> > +++ b/drivers/input/mousedev.c
> > @@ -12,8 +12,8 @@
> >  #define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
> >  
> >  #define MOUSEDEV_MINOR_BASE        32
> > -#define MOUSEDEV_MINORS            32
> > -#define MOUSEDEV_MIX               31
> > +#define MOUSEDEV_MINORS            31
> > +#define MOUSEDEV_MIX               63
> >  
> >  #include <linux/sched.h>
> >  #include <linux/slab.h>
> 
> Thanks.
> 
> --
> Dmitry
> 
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to