[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <16046206.NvsuxYn5NN@vostro.rjw.lan>
Date: Fri, 25 Sep 2015 22:22:33 +0200
From: "Rafael J. Wysocki" <rjw@...ysocki.net>
To: Viresh Kumar <viresh.kumar@...aro.org>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linaro-kernel@...ts.linaro.org,
QCA ath9k Development <ath9k-devel@....qualcomm.com>,
Intel Linux Wireless <ilw@...ux.intel.com>,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-acpi@...r.kernel.org,
linux-bluetooth@...r.kernel.org, iommu@...ts.linux-foundation.org,
netdev@...r.kernel.org, linux-wireless@...r.kernel.org,
linux-scsi@...r.kernel.org, linux-usb@...r.kernel.org,
linux-edac@...r.kernel.org, linux-mm@...ck.org,
alsa-devel@...a-project.org
Subject: Re: [PATCH V4 1/2] ACPI / EC: Fix broken 64bit big-endian users of 'global_lock'
On Friday, September 25, 2015 10:18:13 PM Rafael J. Wysocki wrote:
> On Friday, September 25, 2015 09:41:37 AM Viresh Kumar wrote:
> > global_lock is defined as an unsigned long and accessing only its lower
> > 32 bits from sysfs is incorrect, as we need to consider other 32 bits
> > for big endian 64 bit systems. There are no such platforms yet, but the
> > code needs to be robust for such a case.
> >
> > Fix that by passing a local variable to debugfs_create_bool() and
> > assigning its value to global_lock later.
> >
> > Signed-off-by: Viresh Kumar <viresh.kumar@...aro.org>
>
> Acked-by: Rafael J. Wysocki <rafael.j.wysocki@...el.com>
>
> Greg, please take this one if the [2/2] looks good to you.
Ouch, turns out it was a bad idea. Please scratch that.
Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists