All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Matan Barak <matanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: kbuild test robot
	<fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	kbuild-all-JC7UmRfGjtg@public.gmane.org,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [rdma:k.o/for-next 5/34] drivers/infiniband/hw/hns/hns_roce_device.h:625:2: error: implicit declaration of function '__raw_writeq'
Date: Mon, 14 Aug 2017 11:18:38 -0400	[thread overview]
Message-ID: <1502723918.83939.2.camel@redhat.com> (raw)
In-Reply-To: <20170814145656.GJ24282-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>

On Mon, 2017-08-14 at 17:56 +0300, Leon Romanovsky wrote:
> On Mon, Aug 14, 2017 at 05:47:59PM +0300, Matan Barak wrote:
> > On 14/08/2017 17:40, Doug Ledford wrote:
> > > On 8/12/2017 10:09 PM, kbuild test robot wrote:
> > > > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/dledfor
> > > > d/rdma.git k.o/for-next
> > > > head:   d0d62c34fb746eaf68df5b3d6f4877c7d1e6320c
> > > > commit: e89bf462b6bece63a60723af88c76dce9dbe6b85 [5/34] IB/hns:
> > > > Support compile test for hns RoCE driver
> > > > config: xtensa-allyesconfig (attached as .config)
> > > > compiler: xtensa-linux-gcc (GCC) 4.9.0
> > > > reproduce:
> > > 
> > > Hi Matan,
> > > 
> > > I know you have a fix patch for this on list.  I'll grab it this
> > > week
> > > for sure, so you can ignore this.
> > > 
> > > 
> > 
> > Hi Doug,
> > 
> > Thanks :-)
> > Just to make things easier, this is the link to that patch:
> > https://www.spinics.net/lists/linux-rdma/msg52386.html
> > 
> > In addition, there are a few more patches worth taking to the
> > current RCs
> > that fix kernel crashes:
> > 
> > https://www.spinics.net/lists/linux-rdma/msg52485.html
> > https://www.spinics.net/lists/linux-rdma/msg52722.html
> > 
> > We have another one coming ("IB/uverbs: Fix NULL pointer
> > dereference during
> > device removal"). I guess Leon will post it soon.
> 
> I queued it today [1] and planned to submit it EOW.
> 
> Doug,
> Do you want me to send it earlier?
> 
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/leon/linux-rdma.g
> it/commit/?h=rdma-rc&id=c102f66c43cfc568065df6441890621fb6f03002

Pull it out.  I've already grabbed it off of patchworks and pushed it
out.  I wanted to make sure it hit today's rdma tree in Stephen's for-
next no matter what.

-- 
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
    GPG KeyID: B826A3330E572FDD
    Key fingerprint = AE6B 1BDA 122B 23B4 265B  1274 B826 A333 0E57 2FDD

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2017-08-14 15:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-13  2:09 [rdma:k.o/for-next 5/34] drivers/infiniband/hw/hns/hns_roce_device.h:625:2: error: implicit declaration of function '__raw_writeq' kbuild test robot
     [not found] ` <201708131058.lKYk3TId%fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-08-14 14:40   ` Doug Ledford
     [not found]     ` <5fd6a0f7-cbe4-8bd9-5310-fa2d64ec6829-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-08-14 14:47       ` Matan Barak
     [not found]         ` <4871c56c-ce7a-204a-0d54-5ea5aae604fd-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-08-14 14:56           ` Leon Romanovsky
     [not found]             ` <20170814145656.GJ24282-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-08-14 15:18               ` Doug Ledford [this message]
     [not found]                 ` <1502723918.83939.2.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-08-15  7:52                   ` Leon Romanovsky

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=1502723918.83939.2.camel@redhat.com \
    --to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=kbuild-all-JC7UmRfGjtg@public.gmane.org \
    --cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=matanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.