linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org, heikki.krogerus@linux.intel.com,
	linux-acpi@vger.kernel.org
Subject: Re: [PATCH v2 1/3] device property: add spaces to PROPERTY_ENTRY_STRING macro
Date: Mon, 28 Dec 2015 13:24:13 +0200	[thread overview]
Message-ID: <1451301853.30729.326.camel@linux.intel.com> (raw)
In-Reply-To: <4285778.gtB2L18Hsx@vostro.rjw.lan>

On Mon, 2015-12-28 at 02:12 +0100, Rafael J. Wysocki wrote:
> On Wednesday, December 23, 2015 03:34:42 PM Andy Shevchenko wrote:
> > Just a style fix, no functional changes.
> > 
> > To be folded to Andrew's patch.
> 
> What patch?

In linux-next from Andrew:

e39ece7 include-linux-propertyh-fix-build-issues-with-gcc-444-fix
40bb8a1 include/linux/property.h: fix build issues with gcc-4.4.4

> 
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > ---
> >  include/linux/property.h | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/include/linux/property.h b/include/linux/property.h
> > index b8c4e42..b51fcd3 100644
> > --- a/include/linux/property.h
> > +++ b/include/linux/property.h
> > @@ -230,7 +230,7 @@ struct property_entry {
> >  	.name = _name_,					\
> >  	.length = sizeof(_val_),			\
> >  	.is_string = true,				\
> > -	{ .value = {.str = _val_} },			\
> > +	{ .value = { .str = _val_ } },			\
> >  }
> >  
> >  #define PROPERTY_ENTRY_BOOL(_name_)		\
> > 
> 
> Thanks,
> Rafael
> 

-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-12-28 11:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-23 13:34 [PATCH v2 0/3] device property: post merge fixes Andy Shevchenko
2015-12-23 13:34 ` [PATCH v2 1/3] device property: add spaces to PROPERTY_ENTRY_STRING macro Andy Shevchenko
2015-12-28  1:12   ` Rafael J. Wysocki
2015-12-28 11:24     ` Andy Shevchenko [this message]
2015-12-30  1:49       ` Rafael J. Wysocki
2015-12-30  1:24         ` Andrew Morton
2015-12-30  2:06           ` Rafael J. Wysocki
2015-12-30  1:43             ` Andy Shevchenko
2015-12-30  1:44             ` Andrew Morton
2016-01-01  0:53               ` Rafael J. Wysocki
2015-12-30  1:29         ` Andy Shevchenko
2015-12-23 13:34 ` [PATCH v2 2/3] device property: the secondary fwnode needs to depend on the primary Andy Shevchenko
2015-12-29  8:40   ` Heikki Krogerus
2015-12-29 10:57     ` Andy Shevchenko
2015-12-23 13:34 ` [PATCH v2 3/3] device property: avoid allocations of 0 length Andy Shevchenko

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=1451301853.30729.326.camel@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=sfr@canb.auug.org.au \
    /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).