From: Tyler Hicks <tyhicks@linux.vnet.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: origin tree build warnings
Date: Wed, 29 Apr 2009 10:38:56 -0500 [thread overview]
Message-ID: <49F87490.5090401@linux.vnet.ibm.com> (raw)
In-Reply-To: <20090429005210.3dd9166e.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Wed, 29 Apr 2009 14:44:36 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
>> Hi Tyler,
>>
>> Today's linux-next build (x86_64 allmodconfig) generated these warnings:
>>
>> fs/ecryptfs/inode.c: In function 'ecryptfs_readlink':
>> fs/ecryptfs/inode.c:670: warning: format '%d' expects type 'int', but argument 3 has type 'size_t'
>> fs/ecryptfs/inode.c:693: warning: comparison of distinct pointer types lacks a cast
>>
>> Caused by commit 3a6b42cadc112b01daf0525e5fcd90bb333a5bb3 ("eCryptfs:
>> Larger buffer for encrypted symlink targets").
>
> yup, Randy sent a fix for this today.
>
> I merged that patch and put it into my "to be merged into 2.6.30 via
> the ecryptfs tree" pile.
>
> Tyler, if you can't be bothered setting up a git pull for a one-liner
> then feel free to tell me to merge it.
>
> If you don't do that then I tend to end up sitting on the patch for
> rather a while, sending it at the tree maintainer once every couple of
> weeks. Sometimes I end up sitting on them after the major kernel
> release, after having sent them to the maintainer several times, which
> is all very sad. Sometimes I'll get bored of sending them at the
> maintainer and I'll just merge them anyway, depending upon how frisky
> I'm feeling.
Hi Andrew - I see another warning in Stephen's email that should be
addressed, too. I'll fix that and set up a git pull containing both
fixes a little later today.
Tyler
next prev parent reply other threads:[~2009-04-29 15:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 4:44 linux-next: origin tree build warnings Stephen Rothwell
2009-04-29 7:52 ` Andrew Morton
2009-04-29 15:38 ` Tyler Hicks [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-01 0:42 Stephen Rothwell
2010-01-01 0:50 ` Linus Torvalds
2010-01-01 1:22 ` Stephen Rothwell
2010-01-01 1:32 ` Linus Torvalds
2010-01-01 1:50 ` Stephen Rothwell
2010-01-02 9:32 ` Shilimkar, Santosh
2010-01-04 13:51 ` Samuel Ortiz
2008-12-29 0:35 Stephen Rothwell
2008-12-29 4:01 ` David Miller
2008-12-29 4:17 ` Stephen Rothwell
2008-12-29 4:21 ` David Miller
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=49F87490.5090401@linux.vnet.ibm.com \
--to=tyhicks@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).