linux-kernel - Re: linux-next: build warnings after merge of the tty 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] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 9 Jan 2011 16:56:01 -0800
From:	Greg KH <greg@...ah.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Kay Sievers <kay.sievers@...y.org>,
	Linus <torvalds@...ux-foundation.org>
Subject: Re: linux-next: build warnings after merge of the tty tree

On Mon, Jan 10, 2011 at 11:49:59AM +1100, Stephen Rothwell wrote:
> Hi Greg, Kay,
> 
> On Tue, 21 Dec 2010 11:42:04 -0800 Greg KH <greg@...ah.com> wrote:
> >
> > On Tue, Dec 21, 2010 at 06:11:58PM +1100, Stephen Rothwell wrote:
> > > 
> > > After merging the tty tree, today's linux-next build (powerpc
> > > ppc64_defconfig) produced these warnings:
> > > 
> > > drivers/tty/tty_io.c: In function 'tty_init':
> > > drivers/tty/tty_io.c:3309: warning: ignoring return value of 'device_create_file', declared with attribute warn_unused_result
> > > drivers/tty/vt/vt.c: In function 'vty_init':
> > > drivers/tty/vt/vt.c:2997: warning: ignoring return value of 'device_create_file', declared with attribute warn_unused_result
> > > 
> > > Introduced by commit fbc92a3455577ab17615cbcb91826399061bd789 ("tty: add
> > > 'active' sysfs attribute to tty0 and console device").
> > 
> > Oops, Kay, care to make up a patch to fix these warnings?
> 
> These warnings are now in Linus' tree ...

Yes, Kay just sent me a patch to fix this, which I will queue up after
.38-rc1 is out.

thanks,

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/