linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leon Romanovsky <leonro@mellanox.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: linux-next: Tree for Jan 30 + 20200206 (drivers/infiniband/hw/mlx5/)
Date: Thu, 6 Feb 2020 09:30:19 +0200	[thread overview]
Message-ID: <20200206073019.GC414821@unreal> (raw)
In-Reply-To: <ee5f17b6-3282-2137-7e9d-fa0008f9eeb0@infradead.org>

On Wed, Feb 05, 2020 at 09:31:15PM -0800, Randy Dunlap wrote:
> On 1/30/20 5:47 AM, Randy Dunlap wrote:
> > On 1/29/20 8:28 PM, Stephen Rothwell wrote:
> >> Hi all,
> >>
> >> Please do not add any v5.7 material to your linux-next included
> >> branches until after v5.6-rc1 has been released.
> >>
> >> Changes since 20200129:
> >>
> >
> > on i386:
> >
> > ERROR: "__udivdi3" [drivers/infiniband/hw/mlx5/mlx5_ib.ko] undefined!
> > ERROR: "__divdi3" [drivers/infiniband/hw/mlx5/mlx5_ib.ko] undefined!
> >
> >
> > Full randconfig file is attached.
> >
> >
>
> I am still seeing this on linux-next of 20200206.

Sorry, I was under wrong impression that this failure is connected to
other issue reported by you.

I'm looking on it right now.

Thanks

>
> --
> ~Randy
>

  reply	other threads:[~2020-02-06  7:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-30  4:28 linux-next: Tree for Jan 30 Stephen Rothwell
2020-01-30 13:47 ` linux-next: Tree for Jan 30 (drivers/infiniband/hw/mlx5/) Randy Dunlap
2020-02-06  5:31   ` linux-next: Tree for Jan 30 + 20200206 (drivers/infiniband/hw/mlx5/) Randy Dunlap
2020-02-06  7:30     ` Leon Romanovsky [this message]
2020-02-06 11:40       ` Leon Romanovsky
2020-02-06 14:32         ` Jason Gunthorpe
2020-02-06 14:35           ` Leon Romanovsky
2020-02-06 16:39           ` Randy Dunlap
2020-02-21 13:57     ` Jason Gunthorpe

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=20200206073019.GC414821@unreal \
    --to=leonro@mellanox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --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).