From: domen@coderock.org
To: clemens@endorphin.org
Cc: linux-kernel@vger.kernel.org,
Victor Fusco <victor@cetuc.puc-rio.br>,
domen@coderock.org
Subject: [patch 1/1] dm-crypt: Fix "nocast type" warnings
Date: Thu, 14 Jul 2005 23:42:49 +0200 [thread overview]
Message-ID: <20050714214248.726446000@homer> (raw)
[-- Attachment #1: sparse-drivers_md_dm-crypt --]
[-- Type: text/plain, Size: 767 bytes --]
From: Victor Fusco <victor@cetuc.puc-rio.br>
Fix the sparse warning "implicit cast to nocast type"
File/Subsystem:drivers/md/dm-crypt.c
Signed-off-by: Victor Fusco <victor@cetuc.puc-rio.br>
Signed-off-by: Domen Puncer <domen@coderock.org>
--
---
dm-crypt.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
Index: quilt/drivers/md/dm-crypt.c
===================================================================
--- quilt.orig/drivers/md/dm-crypt.c
+++ quilt/drivers/md/dm-crypt.c
@@ -330,7 +330,7 @@ crypt_alloc_buffer(struct crypt_config *
{
struct bio *bio;
unsigned int nr_iovecs = (size + PAGE_SIZE - 1) >> PAGE_SHIFT;
- int gfp_mask = GFP_NOIO | __GFP_HIGHMEM;
+ unsigned int gfp_mask = GFP_NOIO | __GFP_HIGHMEM;
unsigned int i;
/*
--
reply other threads:[~2005-07-14 21:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050714214248.726446000@homer \
--to=domen@coderock.org \
--cc=clemens@endorphin.org \
--cc=linux-kernel@vger.kernel.org \
--cc=victor@cetuc.puc-rio.br \
/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
all inboxes | Powered by JetHome®