All of lore.kernel.org
 help / color / mirror / Atom feed
From: oulijun <oulijun-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
To: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Linuxarm <linuxarm-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
	linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: 【For help】 some tips for upstream the userspace driver code of hns_roce
Date: Thu, 13 Oct 2016 16:09:46 +0800	[thread overview]
Message-ID: <57FF414A.3000200@huawei.com> (raw)

Hi, Doug Ledford
   Now, I am preparing for upstreaming the userspace driver code of hns_roce.  But, we have
some difficulty how to upstream it. for example,
   i) which branch of ofed should we upstream ?
   ii) if want to upstream the userspace driver of hns_roce successfully, how we should do?

  Can you give me some guides?

thanks
Lijun Ou

--
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

             reply	other threads:[~2016-10-13  8:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-13  8:09 oulijun [this message]
     [not found] ` <57FF414A.3000200-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2016-10-13  9:36   ` 【For help】 some tips for upstream the userspace driver code of hns_roce Leon Romanovsky
     [not found]     ` <20161013093659.GA9282-2ukJVAZIZ/Y@public.gmane.org>
2016-10-13 10:39       ` oulijun
2016-10-14  7:24       ` oulijun
     [not found]         ` <58008835.3060403-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2016-10-14 11:55           ` Leon Romanovsky
2016-10-17 11:29       ` oulijun
     [not found]         ` <5804B615.2010002-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2016-10-18  5:03           ` 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=57FF414A.3000200@huawei.com \
    --to=oulijun-hv44wf8li93qt0dzr+alfa@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linuxarm-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.