From: Greg KH <greg@kroah.com>
To: Arend van Spriel <arend@broadcom.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build warnings after merge of the driver-core tree
Date: Tue, 2 Dec 2014 10:09:49 -0800 [thread overview]
Message-ID: <20141202180949.GA11700@kroah.com> (raw)
In-Reply-To: <547C1C89.1070604@broadcom.com>
On Mon, Dec 01, 2014 at 08:45:13AM +0100, Arend van Spriel wrote:
> On 01-12-14 08:42, Stephen Rothwell wrote:
> > Hi Greg,
> >
> > After merging the driver-core tree, today's linux-next build (arm
> > multi_v7_defconfig) produced this warning:
> >
> > In file included from kernel/power/main.c:16:0:
> > include/linux/debugfs.h:105:10: warning: 'struct device' declared inside parameter list
> > void *data));
> > ^
> >
> > And many more like this.
> >
> > Introduced by commit 98210b7f73f1 ("debugfs: add helper function to
> > create device related seq_file"). See Rule 1 from
> > Documentation/SubmitChecklist - though in this case a simple "struct
> > device;" would probably do.
> >
>
> I submitted a patch for that yesterday [1] and got (automated) email
> from Greg that it is going into his driver-core tree.
>
> Regards,
> Arend
>
> [1] http://mid.gmane.org/1417361481-1136-1-git-send-email-arend@broadcom.com
Sorry for the delay, is now in my driver-core-next branch, so this will
be fixed in the next linux-next pull.
greg k-h
next prev parent reply other threads:[~2014-12-02 18:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 7:42 linux-next: build warnings after merge of the driver-core tree Stephen Rothwell
2014-12-01 7:45 ` Arend van Spriel
2014-12-02 18:09 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-05-21 6:18 Stephen Rothwell
2010-05-21 16:22 ` Chris Wright
2010-05-21 16:47 ` Greg KH
2010-05-21 21:30 ` Jiri Kosina
2010-05-21 22:27 ` Greg KH
2010-05-24 14:03 ` Jiri Kosina
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=20141202180949.GA11700@kroah.com \
--to=greg@kroah.com \
--cc=arend@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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).