From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: linux-next: build warnings after merge of the tty tree
Date: Tue, 21 Dec 2010 11:42:04 -0800 [thread overview]
Message-ID: <20101221194204.GA11611@kroah.com> (raw)
In-Reply-To: <20101221181158.53f62590.sfr@canb.auug.org.au>
On Tue, Dec 21, 2010 at 06:11:58PM +1100, Stephen Rothwell wrote:
> Hi Greg,
>
> 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?
thanks,
greg k-h
next prev parent reply other threads:[~2010-12-21 19:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 7:11 linux-next: build warnings after merge of the tty tree Stephen Rothwell
2010-12-21 19:42 ` Greg KH [this message]
2011-01-10 0:49 ` Stephen Rothwell
2011-01-10 0:51 ` Kay Sievers
2011-01-10 0:56 ` Greg KH
2011-01-10 1:59 ` Stephen Rothwell
2011-01-10 5:49 ` Greg KH
2011-01-10 14:55 ` Kay Sievers
-- strict thread matches above, loose matches on Subject: below --
2015-03-10 5:37 Stephen Rothwell
2018-03-15 6:43 Stephen Rothwell
2018-03-15 17:34 ` Greg KH
2022-05-10 21:58 Stephen Rothwell
2022-05-10 22:46 ` Maciej W. Rozycki
2022-05-11 5:32 ` Greg KH
2022-05-13 22:47 ` Maciej W. Rozycki
2022-06-14 6:47 Stephen Rothwell
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=20101221194204.GA11611@kroah.com \
--to=greg@kroah.com \
--cc=kay.sievers@vrfy.org \
--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