linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: johannes@sipsolutions.net (Johannes Berg)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V4 1/2] ACPI / EC: Fix broken 64bit big-endian users of 'global_lock'
Date: Fri, 25 Sep 2015 20:49:05 +0200	[thread overview]
Message-ID: <1443206945.2161.9.camel@sipsolutions.net> (raw)
In-Reply-To: <20150925184741.GF5951@linux> (sfid-20150925_204744_507179_F4A02CF2)


> Rafael wrote:
> > Actually, what about adding a local u32 variable, say val, here and 
> > doing
> > 
> > >  	if (!debugfs_create_x32("gpe", 0444, dev_dir, (u32 
> > > *)&first_ec->gpe))
> > >  		goto error;
> > >  	if (!debugfs_create_bool("use_global_lock", 0444, 
> > > dev_dir,
> > > -				 (u32 *)&first_ec->global_lock))
> > > +				 &first_ec->global_lock))
> > 
> > 	if (!debugfs_create_bool("use_global_lock", 0444, dev_dir, 
> > &val))
> > 
> > >  		goto error;
> > 
> > 	first_ec->global_lock = val;
> > 
> > And then you can turn val into bool just fine without changing the 
> > structure
> > definition.

Ok, then, but that means Rafael is completely wrong ...
debugfs_create_bool() takes a *pointer* and it needs to be long-lived,
it can't be on the stack. You also don't get a call when it changes.

If you cannot change the struct definition then you must implement a
debugfs file with its own read/write handlers.

johannes

  reply	other threads:[~2015-09-25 18:49 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-25 16:41 [PATCH V4 1/2] ACPI / EC: Fix broken 64bit big-endian users of 'global_lock' 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 [this message]
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
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
     [not found] ` <CAJPN1uvPyZ+hZ64_0ZXU9wPLuAR-qm06GrRmHTjc9+rgiChYDQ@mail.gmail.com>
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=1443206945.2161.9.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).