public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Doug Ledford <dledford@redhat.com>
Cc: Or Gerlitz <gerlitz.or@gmail.com>,
	linux-rdma <linux-rdma@vger.kernel.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PULL REQUEST] Please pull rdma.git
Date: Sun, 20 Nov 2016 14:53:33 +0200	[thread overview]
Message-ID: <20161120125333.GC4946@leon.nu> (raw)
In-Reply-To: <710f3e81-dd9c-8221-cf5e-7a96f4cad5b9@redhat.com>

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

On Sat, Nov 19, 2016 at 06:11:22PM -0500, Doug Ledford wrote:
> On 11/19/2016 2:46 PM, Or Gerlitz wrote:
> > On Fri, Nov 18, 2016 at 4:01 AM, Doug Ledford <dledford@redhat.com> wrote:
> >> On 11/17/2016 5:24 PM, Or Gerlitz wrote:
> >
> > [...]
> > Are you going to comment on that to the submitter? if not, they are
> > going to continue with this practice.
>
> Comment on what to the submitter?  That the patch might not have been
> -rc material?  I would have been OK with it around rc1 or rc2, just not
> this late in the rc cycle.  In the end, I don't, nor can I, rely on
> submitters to determine what's RC material and what isn't, that's what
> I'm supposed to be doing.  I will always apply my own judgment on that
> issue and submitters will learn over time when their patches get skipped
> on any sort of a regular basis.

And I'm pretty fine with Doug's judgement regarding -rc vs. -next. Our
submission flow meets the expected by RDMA maintainer and we will
continue to work in the same mode as long it suits Doug's expectations
for acceptable/unacceptable submission.

>
> > How are we supposed to realize from patchworks + your github branches
> > that patches that were submitted for 4.9-rc are picked for 4.10? this
> > is very confusing and error prone too.
>
> I emailed the submitters off list about it and provided them a list of
> what patches went where and why.

Thank you, I compared the submitted list with found in your trees and
everything looks in place.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-11-20 12:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <58466423-c87e-3921-101e-bffab8989fd8@redhat.com>
     [not found] ` <20161117184950.GP4240@leon.nu>
     [not found]   ` <582E089A.3040106@redhat.com>
     [not found]     ` <20161117200203.GQ4240@leon.nu>
2016-11-17 22:24       ` [PULL REQUEST] Please pull rdma.git Or Gerlitz
2016-11-18  2:01         ` Doug Ledford
2016-11-19 19:46           ` Or Gerlitz
2016-11-19 23:11             ` Doug Ledford
2016-11-20 12:53               ` Leon Romanovsky [this message]
2018-12-13 16:56 Doug Ledford
2018-12-13 21:15 ` pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2019-06-21 19:42 Doug Ledford
2019-06-21 22:35 ` pr-tracker-bot
2019-08-02 14:39 Doug Ledford
2019-08-02 22:10 ` pr-tracker-bot
2019-08-14 14:59 Doug Ledford
2019-08-14 18:25 ` pr-tracker-bot
2019-08-19 10:08 ` Geert Uytterhoeven
2019-08-19 12:14   ` Jason Gunthorpe
2019-08-19 12:29     ` Geert Uytterhoeven
2019-08-19 12:48       ` Jason Gunthorpe
     [not found] <5b0aa103f6007e1887f9b2cacaec8015834589b8.camel@xsintricity.com>
2019-08-23 19:14 ` Doug Ledford
2019-08-30 15:42 Doug Ledford
2019-08-30 16:40 ` pr-tracker-bot

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=20161120125333.GC4946@leon.nu \
    --to=leon@kernel.org \
    --cc=dledford@redhat.com \
    --cc=gerlitz.or@gmail.com \
    --cc=linux-kernel@vger.kernel.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