From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dmitry Torokhov Subject: Re: [PATCH] Input: Fix double equality sign in uevent Date: Sun, 19 Dec 2010 00:04:28 -0800 Message-ID: <20101219080427.GA10074@core.coreip.homeip.net> References: <1292700717-1610-1-git-send-email-rydberg@euromail.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mail-pz0-f42.google.com ([209.85.210.42]:36658 "EHLO mail-pz0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751159Ab0LSIEf (ORCPT ); Sun, 19 Dec 2010 03:04:35 -0500 Content-Disposition: inline In-Reply-To: <1292700717-1610-1-git-send-email-rydberg@euromail.se> Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Henrik Rydberg Cc: Jiri Kosina , linux-input@vger.kernel.org, linux-kernel@vger.kernel.org, stable@kernel.org On Sat, Dec 18, 2010 at 08:31:57PM +0100, Henrik Rydberg wrote: > Looking at the uevent stream for input devices, all properties > are on the form "A=B" except the bitmap values, which are on the > form "A==B". Remedied with this patch. > > Cc: stable@kernel.org > Signed-off-by: Henrik Rydberg > --- > Hi Dmitry, > > Unless the input bitmap properties should really behave differently, > this patch ought to be a candidate for 2.6.37. > Hmm, I do not think so because: - either nobody uses bitmap variables and then it is not priority - users worked around the problem and by applying fix we'd be breaking their setups. I think we should apply it but at the beginning of .38 cycle to give us a chance to evaluate and maybe revert. Does this make sense? -- Dmitry