linux-kernel - Re: linux-next: build warnings after merge of the driver-core tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20141202180949.GA11700@kroah.com>
Date:	Tue, 2 Dec 2014 10:09:49 -0800
From:	Greg KH <greg@...ah.com>
To:	Arend van Spriel <arend@...adcom.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: build warnings after merge of the driver-core tree

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/