All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Triplett <josh@freedesktop.org>
To: Christopher Li <sparse@chrisli.org>
Cc: Anton Altaparmakov <aia21@cam.ac.uk>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-sparse@vger.kernel.org
Subject: Re: Bogus sparse warning?
Date: Tue, 13 Feb 2007 00:22:44 -0800	[thread overview]
Message-ID: <45D17554.5010000@freedesktop.org> (raw)
In-Reply-To: <20070213014657.GA2922@chrisli.org>

[-- Attachment #1: Type: text/plain, Size: 1571 bytes --]

Christopher Li wrote:
> On Tue, Feb 13, 2007 at 12:15:56AM +0000, Anton Altaparmakov wrote:
>> I applied this patch to the current spares git code and reran my test and 
>> now we have two warnings:
>>
>>   CHECK   fs/ntfs/file.c
>> fs/ntfs/file.c:2241:5: warning: incorrect type in argument 8 (different 
>> signedness)
>> fs/ntfs/file.c:2241:5:    expected int [signed] ( [signed] [usertype] 
>> get_block )( ... )
>> fs/ntfs/file.c:2241:5:    got int [signed] ( static [toplevel] *<noident> 
>> )( ... )
>> include/linux/fs.h:1791:14: warning: incorrect type in argument 8 
>> (different signedness)
>> include/linux/fs.h:1791:14:    expected int [signed] ( [signed] [usertype] 
>> get_block )( ... )
>> include/linux/fs.h:1791:14:    got int [signed] ( *get_block )( ... )
>>
>> Best regards,
>>
> 
> I see. In evaluate_call().
> evaluate_arguments() is called before target function arguments
> are converted into pointers.
> 
> Can you please try this patch instead?

Anton reported success with this revision of your patch, so I'd like to apply
it to the sparse tree; could you please supply a Signed-off-by so I can do so?

The same goes for several of the patches in your -cl2 tree, which I would
eagerly like to apply.  Your patches look quite excellent, and greatly advance
the capabilities of Sparse in directions I've wanted to see it progress in.
I'd prefer to pull your patches in as a block, to avoid inconveniencing you by
pulling them in piecemeal and forcing you to rebase the remaining patches.

- Josh Triplett


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  reply	other threads:[~2007-02-13  8:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-12 10:05 Bogus sparse warning? Anton Altaparmakov
2007-02-12 18:28 ` Linus Torvalds
2007-02-12 19:14   ` Christopher Li
2007-02-12 19:53     ` Linus Torvalds
2007-02-13  8:30       ` Josh Triplett
2007-02-13  0:15     ` Anton Altaparmakov
2007-02-13  1:46       ` Christopher Li
2007-02-13  8:22         ` Josh Triplett [this message]
     [not found]           ` <20070213190400.GA9989@chrisli.org>
2007-02-13 23:01             ` Josh Triplett
2007-02-13  9:39         ` Anton Altaparmakov
2007-02-13  0:25   ` Anton Altaparmakov
2007-02-13  0:42     ` Linus Torvalds
2007-02-13  9:53       ` Anton Altaparmakov
2007-02-13 16:10         ` Linus Torvalds
2007-02-13 21:23           ` Anton Altaparmakov

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=45D17554.5010000@freedesktop.org \
    --to=josh@freedesktop.org \
    --cc=aia21@cam.ac.uk \
    --cc=linux-sparse@vger.kernel.org \
    --cc=sparse@chrisli.org \
    --cc=torvalds@linux-foundation.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.