public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Doug Ledford <dledford@redhat.com>
Cc: linux-rdma@vger.kernel.org, devel@driverdev.osuosl.org,
	gregkh@linuxfoundation.org
Subject: Re: HFI1 code duplication todo
Date: Sat, 21 Nov 2015 01:25:23 +0300	[thread overview]
Message-ID: <20151120222523.GX18797@mwanda> (raw)
In-Reply-To: <564F3F1C.4020508@redhat.com>

On Fri, Nov 20, 2015 at 10:41:16AM -0500, Doug Ledford wrote:
> So, as to the hfi1/qib/rxe transport library.  The qib driver is in the
> rdma tree, and we aren't going to move it to staging just because it
> depends on something in staging, so we need to start adding the library
> in the core tree to avoid dependency issues.  As for the hfi1 driver,
> I'm of the opinion that putting it in staging because of the code
> duplication issue was probably not the right thing to do.  It's
> benefited from the extra eyes on it to help make it a better driver, but
> I think I'm ready to move it to the main RDMA tree and start working on
> it from there where there won't be any cross tree dependency issues.

You could leave it staging but manage it from the same git tree.  It
avoids the cross tree dependencies.  This is what we do for
drivers/staging/media/, all that stuff goes through the linux-media
tree.

regards,
dan carpenter

  parent reply	other threads:[~2015-11-20 22:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-12 21:13 HFI1 code duplication todo Dennis Dalessandro
     [not found] ` <20151112211317.GB11252-W4f6Xiosr+yv7QzWx2u06xL4W9x8LtSr@public.gmane.org>
2015-11-19 22:23   ` Dennis Dalessandro
2015-11-20 13:12     ` Dan Carpenter
2015-11-20 15:41     ` Doug Ledford
2015-11-20 15:58       ` ira.weiny
     [not found]       ` <564F3F1C.4020508-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-11-20 15:49         ` Marciniszyn, Mike
2015-11-20 16:39         ` Greg KH
     [not found]           ` <20151120163935.GA10091-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2015-11-20 16:58             ` Doug Ledford
     [not found]               ` <564F512A.1060808-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-11-20 17:01                 ` Christoph Hellwig
2015-11-20 17:13                 ` Greg KH
     [not found]                   ` <20151120171346.GA14829-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2015-11-20 17:46                     ` Doug Ledford
2015-11-20 22:25       ` Dan Carpenter [this message]
2015-11-21 15:53         ` ira.weiny

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=20151120222523.GX18797@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=dledford@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-rdma@vger.kernel.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