From: Jason Wessel <jason.wessel@windriver.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org
Subject: Re: linux-next: build warning
Date: Fri, 29 Aug 2008 07:09:35 -0500 [thread overview]
Message-ID: <48B7E6FF.4010205@windriver.com> (raw)
In-Reply-To: <20080829181433.78a5ae42.sfr@canb.auug.org.au>
Thanks Stephen,
My apologies for introducing the error. This particular patch had not
undergone, final testing before making it to the linux-next tree (IE
checkpatch, boot regression, sparse, code inspection sanity). It
accidentally got pushed while testing all the script changes from
"git-foo" to "git foo".
As a side note, checkpatch tells one to use strict_strtoul instead of
simple_strtoul, but they are obviously not "pin compatible". :-)
Cheers,
Jason.
Stephen Rothwell wrote:
> Hi Jason,
>
> The current linux-next build (x86_64 allmodconfig) gives this warning:
>
> drivers/char/tty_io.c: In function 'tty_find_polling_driver':
> drivers/char/tty_io.c:307: warning: passing argument 2 of 'strict_strtoul' makes integer from pointer without a cast
> drivers/char/tty_io.c:307: warning: passing argument 3 of 'strict_strtoul' makes pointer from integer without a cast
>
> Which points to an actual bug introduced by commit
> 8a89d640448c261c248594511c72db0569725058 ("kgdboc,tty: Fix tty polling
> search to use name correctly") from the kgdb tree.
>
> simple_strtol() and strict_strtoul() take different parameters and have
> different return values.
>
> Warnings are important! Please take a more care.
>
> I will revert that commit from linux-next for today.
>
next prev parent reply other threads:[~2008-08-29 12:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-29 8:14 linux-next: build warning Stephen Rothwell
2008-08-29 12:09 ` Jason Wessel [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-09-18 21:17 Stephen Rothwell
2008-09-27 1:17 ` Steven Rostedt
2008-10-16 6:04 Stephen Rothwell
2008-10-16 16:04 ` Greg KH
2008-11-24 6:38 Stephen Rothwell
2008-11-24 7:53 ` NeilBrown
2008-11-24 9:14 ` Stephen Rothwell
2022-10-10 3:41 Stephen Rothwell
2022-10-10 4:11 ` 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=48B7E6FF.4010205@windriver.com \
--to=jason.wessel@windriver.com \
--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).