From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: oulijun <oulijun-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Cc: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Linuxarm <linuxarm-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: 【For help】 some tips for upstream the userspace driver code of hns_roce
Date: Tue, 18 Oct 2016 08:03:49 +0300 [thread overview]
Message-ID: <20161018050349.GE25013@leon.nu> (raw)
In-Reply-To: <5804B615.2010002-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1923 bytes --]
On Mon, Oct 17, 2016 at 07:29:25PM +0800, oulijun wrote:
> 在 2016/10/13 17:36, Leon Romanovsky 写道:
> > On Thu, Oct 13, 2016 at 04:09:46PM +0800, oulijun wrote:
> >> 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?
> >
> > Hi Lijun,
> >
> > Our main library for all user-space stack is located at github [1].
> > Please see similar question from Ram [2] and Jason's response [3] to it.
> >
> > [1] github.com/linux-rdma/rdma-core
> > [2[ http://marc.info/?l=linux-rdma&m=147574131706820&w=2
> > [3] http://marc.info/?l=linux-rdma&m=147577168016989&w=2
> >
> > Thanks.
> >
> >>
> >> thanks
> >> Lijun Ou
> >>
> Hi, leon
> if i will upstream the patch for user-space code, how to guarantee the code format satisfied the rdma-core.git?
> As is known to all, the kernel driver code will be checked by checkpatch.pl, the rdma-core.git also use the
> checkpatch.pl script?
There is no strict enforcement for specific coding style in this
package and we don't have checkpatch-like utility for rdma-core.
I would be happy to see kernel coding style in this repository, but
won't prevent acceptance for code which is written in other adequate style
(constant across new code and clear to read).
It can be changed in the future, once we decide to unify coding style in
rdma-core, but we are not there yet.
>
> thanks
>
> >> --
> >> 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
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-10-18 5:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 8:09 【For help】 some tips for upstream the userspace driver code of hns_roce oulijun
[not found] ` <57FF414A.3000200-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2016-10-13 9:36 ` 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 [this message]
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=20161018050349.GE25013@leon.nu \
--to=leon-dgejt+ai2ygdnm+yrofe0a@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 \
--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 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).