From: Theodore Ts'o <tytso@mit.edu>
To: Fabian Frederick <fabf@skynet.be>
Cc: linux-kernel@vger.kernel.org,
Andreas Dilger <adilger.kernel@dilger.ca>,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH 1/1 linux-next] ext4: fix incorrect type argument
Date: Mon, 8 Jun 2015 12:21:57 -0400 [thread overview]
Message-ID: <20150608162157.GI19168@thunk.org> (raw)
In-Reply-To: <1431723673-25450-1-git-send-email-fabf@skynet.be>
On Fri, May 15, 2015 at 11:01:13PM +0200, Fabian Frederick wrote:
> Fix sparse warning introduced in commit
> 9bd8212f981e
> ("ext4 crypto: add encryption policy and password salt support")
>
> fs/ext4/ioctl.c:678:35: warning: incorrect type in argument 1
> (different address spaces)
> fs/ext4/ioctl.c:678:35: expected void [noderef] <asn:1>*to
> fs/ext4/ioctl.c:678:35: got void *<noident>
>
> Signed-off-by: Fabian Frederick <fabf@skynet.be>
Thanks for pointing this out! I'll fix this and another sparse
warning at the same time.
- Ted
prev parent reply other threads:[~2015-06-08 16:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 21:01 [PATCH 1/1 linux-next] ext4: fix incorrect type argument Fabian Frederick
2015-06-08 16:21 ` Theodore Ts'o [this message]
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=20150608162157.GI19168@thunk.org \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=fabf@skynet.be \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 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).