From: Alasdair G Kergon <agk@redhat.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
dm-devel@redhat.com, linux-next@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [dm-devel] linux-next: Tree for January 12 (dm-crypt)
Date: Wed, 12 Jan 2011 23:12:15 +0000 [thread overview]
Message-ID: <20110112231215.GC9501@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <20110112100121.ba610465.randy.dunlap@oracle.com>
On Wed, Jan 12, 2011 at 10:01:21AM -0800, Randy Dunlap wrote:
> When CONFIG_LBDAF is not enabled (build on i386):
> (sector_t is 32 bits)
>
> drivers/md/dm-crypt.c:568: warning:right shift count >= width of type
Thanks - being fixed.
Alasdair
next prev parent reply other threads:[~2011-01-12 23:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 3:18 linux-next: Tree for January 12 Stephen Rothwell
2011-01-12 18:01 ` linux-next: Tree for January 12 (dm-crypt) Randy Dunlap
2011-01-12 23:12 ` Alasdair G Kergon [this message]
2011-01-12 20:20 ` [PATCH -next] x86/e820: fix build when ACPI is disabled Randy Dunlap
2011-01-12 20:35 ` Rafael J. Wysocki
2011-01-12 20:49 ` Randy Dunlap
2011-01-12 21:03 ` [PATCH] ACPI / PM: Fix build problems for !CONFIG_ACPI related to NVS rework Rafael J. Wysocki
2011-01-12 21:12 ` Len Brown
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=20110112231215.GC9501@agk-dp.fab.redhat.com \
--to=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--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