mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Devesh Sharma <Devesh.Sharma@Emulex.Com>
To: Roland Dreier <roland@kernel.org>
Cc: "Nicholas A. Bellinger" <nab@linux-iscsi.org>,
	Or Gerlitz <or.gerlitz@gmail.com>,
	Hefty Sean <sean.hefty@intel.com>,
	linux-rdma <linux-rdma@vger.kernel.org>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	target-devel <target-devel@vger.kernel.org>,
	Sagi Grimberg <sagig@mellanox.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: RE: linux rdma 3.14 merge plans
Date: Mon, 10 Mar 2014 09:00:38 +0000	[thread overview]
Message-ID: <EE7902D3F51F404C82415C4803930ACD3FDDE3DE@CMEXMB1.ad.emulex.com> (raw)
In-Reply-To: <CAL1RGDXRCZafDcFsbiG823VQ7_AVZeZqxY8JEaj=oCYRteAw_A@mail.gmail.com>

Thanks Roland,
My response is inline below.

-Regards
 Devesh
-----Original Message-----
From: roland@purestorage.com [mailto:roland@purestorage.com] On Behalf Of Roland Dreier
Sent: Saturday, March 08, 2014 1:02 AM
To: Devesh Sharma
Cc: Nicholas A. Bellinger; Or Gerlitz; Hefty Sean; linux-rdma; Martin K. Petersen; target-devel; Sagi Grimberg; linux-kernel
Subject: Re: linux rdma 3.14 merge plans

Sure, no problem.

Do you have a git tree with the latest versions of all the changes you want for 3.15 in a branch?  That would be helpful as I catch up on applying things, so that I don't miss anything.
[DS]: Yes, I do have a cloned copy of your git tree migrated to for-next branch, with all the patches we have submitted to linux-rdma (patch series: [PATCH for-next 00/17] ocrdma driver code sync-up). However, it is on my local server.
In case of urgency (and if OFED EWG permits me) I can set it up on benay dot openfabrics dot org, for now and give a link to pull.

If you don't have one, taking a little time to set one up on github or wherever would be nice.  You can base your set of changes on Linus's latest tree.
[DS]: Currently we do not have such tree. I will have to discuss within my organization on how to go about this request. 

Thanks!
  Roland

On Thu, Mar 6, 2014 at 9:07 PM, Devesh Sharma <Devesh.Sharma@emulex.com> wrote:
> Hi Roland,
>
> Is it okay to send next series of patches even if previous series is not accepted yet in your tree? Off-course I will cut patches on top of previous series of patches.
>
> -Regards
>  Devesh
>
> -----Original Message-----
> From: linux-rdma-owner@vger.kernel.org 
> [mailto:linux-rdma-owner@vger.kernel.org] On Behalf Of Nicholas A. 
> Bellinger
> Sent: Thursday, March 06, 2014 12:34 AM
> To: Roland Dreier
> Cc: Or Gerlitz; Hefty Sean; linux-rdma; Martin K. Petersen; 
> target-devel; Sagi Grimberg; linux-kernel
> Subject: Re: linux rdma 3.14 merge plans
>
> On Wed, 2014-03-05 at 07:18 -0800, Roland Dreier wrote:
>> On Wed, Mar 5, 2014 at 1:54 AM, Nicholas A. Bellinger 
>> <nab@linux-iscsi.org> wrote:
>> > That all said, do you have an objection wrt taking this bits 
>> > through target-pending..?  Given the dependencies involved, that 
>> > would seem the most logical path to take.
>>
>> Perhaps not surprisingly, I would prefer to get a chance to review a 
>> major change to the core RDMA midlayer rather than having you merge 
>> it through your tree.  So yes I do object.  Please give me a chance 
>> to review and merge it.  I am working on that this week.
>>
>
> Great.  We'll be looking for a response by the end of the week.
>
> Otherwise if you end up not having time, we'd still like to move forward for v3.15 given the amount of review the series has already gotten on the list.
>
> Thank you,
>
> --nab
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" 
> in the body of a message to majordomo@vger.kernel.org More majordomo 
> info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2014-03-10  9:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJZOPZ+4yQ-sT=ks7+eiJjkxOjy5w=BmG16JVcUPiuVsof7qEA@mail.gmail.com>
     [not found] ` <CAG4TOxOMmvFWnkU3DBn33rscEKh2_YfbUCKY=iY8PCVN3+nEsA@mail.gmail.com>
     [not found]   ` <52CD1C68.4050406@mellanox.com>
     [not found]     ` <1389645171.5567.459.camel@haakon3.risingtidesystems.com>
     [not found]       ` <1389820541.5567.543.camel@haakon3.risingtidesystems.com>
     [not found]         ` <CAG4TOxNa32sLxifPx_f8sW04B_qSh01WWfWjRvam6fjvFLDXSQ@mail.gmail.com>
     [not found]           ` <1389906852.5567.668.camel@haakon3.risingtidesystems.com>
     [not found]             ` <CAG4TOxPeYQ=e5LdJft1Hkx8donUQjJaKDEAv3iRLGxPYJQ_b9w@mail.gmail.com>
     [not found]               ` <1390102949.5567.749.camel@haakon3.risingtidesystems.com>
     [not found]                 ` <52DBB4F1.4020400@mellanox.com>
     [not found]                   ` <CAJZOPZJFbcTh2zO8mos0M+gv0LW-Gmh877Vxe4tLvfPX19oqTw@mail.gmail.com>
2014-01-21 22:00                     ` Or Gerlitz
2014-01-22  0:43                       ` Roland Dreier
2014-01-22  4:10                         ` Or Gerlitz
2014-01-22  7:27                         ` Nicholas A. Bellinger
2014-02-07  0:02                           ` Nicholas A. Bellinger
2014-02-07  0:04                             ` Roland Dreier
2014-02-25 21:10                               ` Or Gerlitz
2014-03-05  9:54                               ` Nicholas A. Bellinger
2014-03-05 15:18                                 ` Roland Dreier
2014-03-05 15:38                                   ` Or Gerlitz
2014-03-05 19:03                                   ` Nicholas A. Bellinger
2014-03-07  5:07                                     ` Devesh Sharma
2014-03-07 19:31                                       ` Roland Dreier
2014-03-10  9:00                                         ` Devesh Sharma [this message]
     [not found]                         ` <52DF93D3.6030509@dev.mellanox.co.il>
2014-01-28 21:02                           ` Or Gerlitz

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=EE7902D3F51F404C82415C4803930ACD3FDDE3DE@CMEXMB1.ad.emulex.com \
    --to=devesh.sharma@emulex.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=nab@linux-iscsi.org \
    --cc=or.gerlitz@gmail.com \
    --cc=roland@kernel.org \
    --cc=sagig@mellanox.com \
    --cc=sean.hefty@intel.com \
    --cc=target-devel@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

all inboxes | Powered by JetHome®