From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linaro-kernel@lists.linaro.org,
Viresh Kumar <viresh.kumar@linaro.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"open list:NETWORKING DRIVERS (WIRELESS)"
<linux-wireless@vger.kernel.org>,
"moderated list:SOUND - SOC LAYER / DYNAMIC AUDIO POWER
MANAGEM..." <alsa-devel@alsa-project.org>,
"open list:TARGET SUBSYSTEM" <linux-scsi@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"open list:ULTRA-WIDEBAND (UWB) SUBSYSTEM:"
<linux-usb@vger.kernel.org>,
QCA ath9k Development <ath9k-devel@qca.qualcomm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Intel Linux Wireless <ilw@linux.intel.com>,
Linux ACPI <linux-acpi@vger.kernel.org>,
"open list:AMD IOMMU (AMD-VI)" <iommu@lists.linux-foundation.org>,
"open list:BLUETOOTH DRIVERS" <linux-bluetooth@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Johannes Berg <johannes@sipsolutions.net>,
Linux Memory Management List <linux-mm@kvack.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"open list:EDAC-CORE" <linux-edac@vger.kernel.org>
Subject: Re: [PATCH V4 1/2] ACPI / EC: Fix broken 64bit big-endian users of 'global_lock'
Date: Sun, 27 Sep 2015 16:10:48 +0200 [thread overview]
Message-ID: <1578470.DLzaBp4j3T@vostro.rjw.lan> (raw)
In-Reply-To: <1540878.9slRi6Q7xb@wuerfel>
On Saturday, September 26, 2015 09:33:56 PM Arnd Bergmann wrote:
> On Saturday 26 September 2015 11:40:00 Viresh Kumar wrote:
> > On 25 September 2015 at 15:19, Rafael J. Wysocki <rafael@kernel.org> wrote:
> > > So if you allow something like debugfs to update your structure, how
> > > do you make sure there is the proper locking?
> >
> > Not really sure at all.. Isn't there some debugfs locking that will
> > jump in, to avoid updation of fields to the same device?
>
> No, if you need any locking to access variable, you cannot use the
> simple debugfs helpers but have to provide your own functions.
>
> > >> Anyway, that problem isn't here for sure as its between two
> > >> unsigned-longs. So, should I just move it to bool and resend ?
> > >
> > > I guess it might be more convenient to fold this into the other patch,
> > > because we seem to be splitting hairs here.
> >
> > I can and that's what I did. But then Arnd asked me to separate it
> > out. I can fold it back if that's what you want.
>
> It still makes sense to keep it separate I think, the patch is clearly
> different from the other parts.
I just don't see much point in going from unsigned long to u32 and then
from 32 to bool if we can go directly to bool in one go.
Thanks,
Rafael
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-09-27 13:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 16:41 Viresh Kumar
2015-09-25 16:41 ` [PATCH V4 2/2] debugfs: Pass bool pointer to debugfs_create_bool() Viresh Kumar
2015-09-25 17:42 ` [PATCH V4 1/2] ACPI / EC: Fix broken 64bit big-endian users of 'global_lock' Johannes Berg
2015-09-25 18:47 ` Viresh Kumar
2015-09-25 18:49 ` Johannes Berg
2015-09-25 18:52 ` Viresh Kumar
2015-09-25 20:26 ` Rafael J. Wysocki
2015-09-25 20:33 ` Rafael J. Wysocki
2015-09-25 20:25 ` Viresh Kumar
2015-09-25 20:58 ` Rafael J. Wysocki
2015-09-25 21:44 ` Viresh Kumar
2015-09-25 22:19 ` Rafael J. Wysocki
2015-09-26 18:40 ` Viresh Kumar
2015-09-26 19:33 ` Arnd Bergmann
2015-09-27 14:10 ` Rafael J. Wysocki [this message]
2015-09-28 8:24 ` Arnd Bergmann
2015-09-28 13:07 ` Rafael J. Wysocki
2015-09-26 19:52 ` James Bottomley
2015-09-27 14:09 ` Rafael J. Wysocki
2015-09-28 8:58 ` David Laight
2015-09-28 14:26 ` James Bottomley
2015-09-28 14:50 ` David Laight
2015-09-28 15:11 ` James Bottomley
2015-09-28 15:31 ` David Laight
2015-09-25 20:18 ` Rafael J. Wysocki
2015-09-25 20:22 ` Rafael J. Wysocki
2015-09-27 5:31 ` Jiri Slaby
2015-09-27 14:35 ` Viresh Kumar
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=1578470.DLzaBp4j3T@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=alsa-devel@alsa-project.org \
--cc=arnd@arndb.de \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=gregkh@linuxfoundation.org \
--cc=ilw@linux.intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=johannes@sipsolutions.net \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=viresh.kumar@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox