All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Dennis Dalessandro <dennis.dalessandro@intel.com>
Cc: linux-rdma@vger.kernel.org, devel@driverdev.osuosl.org,
	dledford@redhat.com, gregkh@linuxfoundation.org
Subject: Re: HFI1 code duplication todo
Date: Fri, 20 Nov 2015 16:12:31 +0300	[thread overview]
Message-ID: <20151120131231.GW18797@mwanda> (raw)
In-Reply-To: <20151119222319.GA17605@phlsvsds.ph.intel.com>

At the beginning when hfi1 was put into staging, then it was easy enough
for Greg to take those patches but now it feels awkward.  Probably
Doug and the linux-rdma@vger.kernel.org people should start maintaining
the drivers/staging/rdma directory.  Like merge Greg's tree and pull in
whatever checkpatch fixes are still on the list and then take over from
there...

regards,
dan carpenter

  reply	other threads:[~2015-11-20 13:12 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 [this message]
2015-11-20 15:41     ` Doug Ledford
     [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 15:58       ` ira.weiny
2015-11-20 22:25       ` Dan Carpenter
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=20151120131231.GW18797@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=dennis.dalessandro@intel.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 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.