From: "Wei Hu (Xavier)" <xavier.huwei-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
To: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
oulijun <oulijun-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: "Chenxin (Charles)"
<charles.chenxin-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
weihaifeng <haifeng.wei-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
liudongdong
<liudongdong3-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Subject: Re: 【Ask for upstream branch】
Date: Thu, 24 Aug 2017 15:35:11 +0800 [thread overview]
Message-ID: <599E81AF.5040901@huawei.com> (raw)
In-Reply-To: <546382b6-7cdc-9277-c0b8-130d58136a88-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On 2017/8/21 20:57, Doug Ledford wrote:
> On 8/21/2017 2:16 AM, oulijun wrote:
>> Hi, Doug Ledford
>>
>> We are preparing the hip08 RoCE driver for upstreaming. I am found that
>>
>> you have create a new branch named net-next-base and this branch has
>> included
>>
>> hns3 patchset. If we generate patchset of hip08 RoCE driver, can
>> directly based
>>
>> on this branch?
> Yes.
>
Hi, Doug
In the repo
https://git.kernel.org/pub/scm/linux/kernel/git/dledford/rdma.git,
we found for-next-merged branch looks newer than k.o/net-next-base,
right ?
please reconfirm which branch we should generate patcheset based on.
Thank you very much!
1. k.o/for-next-merged branch
git log --oneline drivers/infiniband/hw/hns/
b0e32e2 Merge branch 'k.o/for-4.13-rc' into k.o/for-next
5b59a39 IB/hns: fix memory leak on ah on error return path
3e5f088 IB/hns: Avoid compile test under non 64bit environments
8ccf098 Revert "RDMA/hns: fix build regression"
5db465f IB/hns: checking for IS_ERR() instead of NULL
967de35 IB/hns: include linux/interrupt.h
ecd840f RDMA/hns: fix build regression
d1d7149 IB/hns: fix semicolon.cocci warnings
87809f8 IB/hns: fix returnvar.cocci warnings
3756c7f IB/hns: fix boolreturn.cocci warnings
e89bf46 IB/hns: Support compile test for hns RoCE driver
5f110ac4 IB/hns: Fix for checkpatch.pl comment style warnings
d322f00 IB/hns: Fix the bug with modifying the MAC address without
removing the driver
9de61d3 IB/hns: Fix the bug with rdma operation
58c4f0d IB/hns: Fix the bug with wild pointer when destroy rc qp
2. k.o/net-next-base
git log --oneline drivers/infiniband/hw/hns/
5db465f IB/hns: checking for IS_ERR() instead of NULL
5f110ac4 IB/hns: Fix for checkpatch.pl comment style warnings
d322f00 IB/hns: Fix the bug with modifying the MAC address without
removing the driver
9de61d3 IB/hns: Fix the bug with rdma operation
58c4f0d IB/hns: Fix the bug with wild pointer when destroy rc qp
Regards
Wei Hu
--
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
next prev parent reply other threads:[~2017-08-24 7:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <33078683-cf77-a116-4245-f561a29b114d@huawei.com>
[not found] ` <33078683-cf77-a116-4245-f561a29b114d-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2017-08-21 12:57 ` 【Ask for upstream branch】 Doug Ledford
[not found] ` <546382b6-7cdc-9277-c0b8-130d58136a88-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-08-24 7:35 ` Wei Hu (Xavier) [this message]
[not found] ` <599E81AF.5040901-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2017-08-24 8:34 ` oulijun
[not found] ` <a6ed9854-46f0-77be-a708-de7b2100a58c-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2017-08-24 19:31 ` Doug Ledford
[not found] ` <1503603071.78641.35.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-08-29 1:01 ` Wei Hu (Xavier)
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=599E81AF.5040901@huawei.com \
--to=xavier.huwei-hv44wf8li93qt0dzr+alfa@public.gmane.org \
--cc=charles.chenxin-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=haifeng.wei-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=liudongdong3-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
--cc=oulijun-hv44wF8Li93QT0dZR+AlfA@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.