From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Joe Thornber <dm-devel@redhat.com>,
Alasdair Kergon <agk@redhat.com>
Subject: Re: linux-next: Tree for Jun 27 (dm-thin.c)
Date: Wed, 27 Jun 2012 09:13:33 -0700 [thread overview]
Message-ID: <4FEB312D.5020608@xenotime.net> (raw)
In-Reply-To: <20120627132217.f8bbdd1f467711419123d188@canb.auug.org.au>
On 06/26/2012 08:22 PM, Stephen Rothwell wrote:
> Hi all,
>
> This tree was not built between each merge, but only after merging all
> the trees.
>
> Changes since 20120626:
>
> The device-mapper tree gained a build failure for which I reverted a
> commit.
on x86_64:
drivers/md/dm-thin.c: In function 'pool_preresume':
drivers/md/dm-thin.c:2129:3: warning: format '%llu' expects type 'long long unsigned int', but argument 2 has type 'sector_t'
CONFIG_LBDAF is not enabled.
--
~Randy
next parent reply other threads:[~2012-06-27 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120627132217.f8bbdd1f467711419123d188@canb.auug.org.au>
2012-06-27 16:13 ` Randy Dunlap [this message]
2012-06-27 16:18 ` linux-next: Tree for Jun 27 (dm-thin.c) Alasdair G Kergon
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=4FEB312D.5020608@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--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).