From: Johan Hovold <jhovold@gmail.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: Johan Hovold <jhovold@gmail.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] mfd: lm3533: fix return type of attribute is_visible
Date: Mon, 21 May 2012 10:46:20 +0200 [thread overview]
Message-ID: <20120521084620.GC21033@localhost> (raw)
In-Reply-To: <20120520131908.GV12015@sortiz-mobl>
On Sun, May 20, 2012 at 03:19:08PM +0200, Samuel Ortiz wrote:
> Hi Johan,
>
> On Fri, May 18, 2012 at 01:18:04PM +0200, Johan Hovold wrote:
> > Hi Samuel,
> >
> > On Fri, May 11, 2012 at 10:40:41AM +0200, Johan Hovold wrote:
> > > Since commit 587a1f1659 ("switch ->is_visible() to returning umode_t")
> > > the return type of is_visible is umode_t rather than mode_t.
> > >
> > > This silences a compiler warning on some architectures where these types
> > > are not compatible.
> > >
> > > Reported-by: Andrew Morton <akpm@linux-foundation.org>
> > > Signed-off-by: Johan Hovold <jhovold@gmail.com>
> > > ---
> >
> > Apparently Dan Carpenter sent a fix for this compiler warning the day
> > after I submitted mine. Dan's patch, however, only fixed the return type
> > and not the type of the mode variable.
> >
> > Could you consider applying this patch one on top of Dan's (which you
> > applied to mfd-next on Monday)?
> I applied the following chunk:
>
> @@ -367,7 +367,7 @@ static umode_t lm3533_attr_is_visible(struct kobject *kobj,
> struct device_attribute *dattr = to_dev_attr(attr);
> struct lm3533_device_attribute *lattr = to_lm3533_dev_attr(dattr);
> enum lm3533_attribute_type type = lattr->type;
> - mode_t mode = attr->mode;
> + umode_t mode = attr->mode;
Great. Thanks!
Johan
prev parent reply other threads:[~2012-05-21 8:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 8:40 [PATCH] mfd: lm3533: fix return type of attribute is_visible Johan Hovold
2012-05-18 11:18 ` Johan Hovold
2012-05-20 13:19 ` Samuel Ortiz
2012-05-21 8:46 ` Johan Hovold [this message]
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=20120521084620.GC21033@localhost \
--to=jhovold@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.com \
/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