Re: [PATCH rdma-next] RDMA/qedr: Fix rdma_type initialization

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 2017-09-26 at 09:10 +0300, Leon Romanovsky wrote:
> On Mon, Sep 25, 2017 at 08:29:58AM -0400, Dennis Dalessandro wrote:
> > On 9/20/2017 1:42 AM, Kalderon, Michal wrote:
> > > From: Leon Romanovsky <leon@xxxxxxxxxx>
> > > Sent: Tuesday, September 19, 2017 8:47 PM
> > > 
> > > On Tue, Sep 19, 2017 at 08:38:37PM +0300, Michal Kalderon wrote:
> > > > > Initialize the rdma_type (iWARP or RoCE) which is set
> > > > > according to
> > > > > device configuration in qed.
> > > > > 
> > > > > Signed-off-by: Michal Kalderon <Michal.Kalderon@xxxxxxxxxx>
> > > > > Signed-off-by: Ariel Elior <Ariel.Elior@xxxxxxxxxx>
> > > > > ---
> > > > 
> > > > Please add Fixes.
> > > > 
> > > > Thanks
> > > 
> > > sure, i'll send v1
> > 
> > Does just responding with a "Fixes" tag get appended automagically
> > by
> > Patchworks?
> 
> I don't think so, but let's check with fixes line from v1.
> Fixes: e6a38c54faf ("RDMA/qedr: Add support for registering an iWARP
> device")

Patchworks does, in fact, add the Fixes: line (although not in the
format we normally tell people to use as there is empty space between
the Fixes: line and the start of the Signed-off-by: lines).

However, that's all irrelevant, as this patch breaks the build for me. 
Is there a prerequisite patch in net-next for this?

-- 
Doug Ledford <dledford@xxxxxxxxxx>
    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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Photo]     [Yosemite News]     [Yosemite Photos]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux