All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Greg KH <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
Cc: Dennis Dalessandro
	<dennis.dalessandro-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	devel-gWbeCf7V1WCQmaza687I9mD2FQJk+8+b@public.gmane.org,
	ira.weiny-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
	mike.marciniszyn-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Subject: Re: HFI1 code duplication todo
Date: Fri, 20 Nov 2015 11:58:18 -0500	[thread overview]
Message-ID: <564F512A.1060808@redhat.com> (raw)
In-Reply-To: <20151120163935.GA10091-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 2361 bytes --]

On 11/20/2015 11:39 AM, Greg KH wrote:
> On Fri, Nov 20, 2015 at 10:41:16AM -0500, Doug Ledford wrote:
>> To that end, I've opened my 4.4-rc branch and deleted the three
>> deprecated drivers from staging and moved hfi1 to the rdma tree.  I've
>> sent an email to Linus to see if he's ok taking those changes, and if
>> so, I'll get them submitted and then open up my for-4.5 branch early to
>> be able to start taking for-next patches.
> 
> I think it's too late for that, especially given that I have 34+ patches
> for the staging rdma drivers already in my tree in linux-next.

For hfi1 rename detection should work, for the other three, patches to
removed files are easily resolved as simply dropped patches.  So I don't
think it's that large of an issue.  Correct me if I'm wrong.

>  And the
> hfil1 code really doesn't look like its ready to merge into the "real"
> portion of the kernel tree, given the horrid nature of the patches
> submitted recently for it :(

I'm sorry, that doesn't make sense to me.  How can the quality of
patches that aren't part of the driver yet and are just being submitted
impune the readiness of the code the patches are supposed to be touching?

And that's orthogonal to the issue that the primary TODO item for this
driver requires coordination between it, qib (in the RDMA tree), and the
upcoming soft_roce driver.  If the driver isn't moved, then we have to
coordinate between your tree and mine to make sure that no patches are
taken into your tree until after the patches they depend on have landed
in my tree.  And then you tree likely won't build unless you pull from
my tree and merge up first.  It's not really tenable.  That was why I
had suggested (and originally you agreed to) that I would handle the
entire staging/rdma tree.  However, since you changed your mind on that
issue, we now have this coordination issue.  I don't really want to deal
with that, so I would rather move the hfi1 driver and take care of the
all the needed patching myself going forward.

> I had expected the drivers to be deleted for -rc1, removing them now
> seems a bit late in the merge window.

Yes, I know.  I've been busy.  My apologies for not getting it in prior
to rc1.

-- 
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
              GPG KeyID: 0E572FDD



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]

  parent reply	other threads:[~2015-11-20 16:58 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
     [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 [this message]
     [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=564F512A.1060808@redhat.com \
    --to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=dennis.dalessandro-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=devel-gWbeCf7V1WCQmaza687I9mD2FQJk+8+b@public.gmane.org \
    --cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
    --cc=ira.weiny-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mike.marciniszyn-ral2JQCrhuEAvxtiuMwx3w@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.