linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Alasdair G Kergon <agk@redhat.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Joe Thornber <dm-devel@redhat.com>,
	Mikulas Patocka <mpatocka@redhat.com>
Subject: Re: linux-next: Tree for Nov 15 (drivers/md/dm-integrity)
Date: Fri, 15 Nov 2019 18:10:51 -0500	[thread overview]
Message-ID: <20191115231050.GA29649@redhat.com> (raw)
In-Reply-To: <20191116094620.497663ab@canb.auug.org.au>

On Fri, Nov 15 2019 at  5:46pm -0500,
Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi all,
> 
> On Fri, 15 Nov 2019 08:17:48 -0800 Randy Dunlap <rdunlap@infradead.org> wrote:
> >
> > on i386:
> > 
> > ld: drivers/md/dm-integrity.o: in function `calculate_device_limits':
> > dm-integrity.c:(.text.unlikely+0x1e9): undefined reference to `__udivdi3'
> 
> Caused by commit
> 
>   a236c37603bd ("dm integrity: fix excessive alignment of metadata runs")
> 
> From the device-mapper tree.

Yes, I've pushed a fixed commit, please see:
https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=for-next&id=d537858ac8aaf4311b51240893add2fc62003b97


  reply	other threads:[~2019-11-15 23:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-15  8:05 linux-next: Tree for Nov 15 Stephen Rothwell
2019-11-15 16:02 ` linux-next: Tree for Nov 15 (objtool) Randy Dunlap
2019-11-15 16:38   ` Josh Poimboeuf
2020-01-20 15:37     ` Josh Poimboeuf
2019-11-15 16:11 ` linux-next: Tree for Nov 15 Naresh Kamboju
2019-11-15 16:17 ` linux-next: Tree for Nov 15 (drivers/md/dm-integrity) Randy Dunlap
2019-11-15 16:19   ` Randy Dunlap
2019-11-15 19:27     ` Mike Snitzer
2019-11-18 16:32     ` Alasdair G Kergon
2019-11-15 22:46   ` Stephen Rothwell
2019-11-15 23:10     ` Mike Snitzer [this message]
2019-11-15 23:32       ` Stephen Rothwell
2019-11-15 16:35 ` linux-next: Tree for Nov 15 (sound/soc/codecs/rt5677) Randy Dunlap
2019-11-15 23:44 ` linux-next: Tree for Nov 15 (thermal: THERMAL_GOV_POWER_ALLOCATOR) Randy Dunlap
2019-12-04 16:25   ` Randy Dunlap
2019-12-05  4:27     ` Zhang Rui
2019-12-05  4:36       ` Quentin Perret
2019-12-05  5:50         ` Zhang Rui
2019-12-05  5:47       ` Randy Dunlap

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=20191115231050.GA29649@redhat.com \
    --to=snitzer@redhat.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mpatocka@redhat.com \
    --cc=rdunlap@infradead.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).