From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH rdma-next v1 0/6] RDMA core and mlx5 fixes and refactoring for 4.15
Date: Wed, 18 Oct 2017 12:20:27 -0400 [thread overview]
Message-ID: <1508343627.2951.4.camel@redhat.com> (raw)
In-Reply-To: <20171018154006.GS2106-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
On Wed, 2017-10-18 at 18:40 +0300, Leon Romanovsky wrote:
> On Wed, Oct 18, 2017 at 11:25:09AM -0400, Doug Ledford wrote:
> > On Mon, 2017-10-16 at 08:45 +0300, Leon Romanovsky wrote:
> > > The patches are available in the git repository at:
> > > git.kernel.org/pub/scm/linux/kernel/git/leon/linux-rdma.git
> > > tags/rdma-next-2017-10-16
> >
> > This branch is unpullable for me. Trying to pull this on top of
> > the
> > shared pull request brings in a ton of other stuff. My diffstat
> > ends
> > up looking like this:
>
> <....>
>
> >
> > So, with a shared pull request, your submissions either need to be
> > against that shared pull request, or against my for-next, and you
> > need
> > to let me know which one it is.
>
> I didn't know that you are using this as a pull request, we tried it
> in
> last cycle and it didn't truly work, so I stopped it and changed the
> title
> (instead of pull requests, it is patches now), removed invitation to
> pull from
> the cover letter and prepared the series (with tags) as standalone
> patches
> and not as pull request.
OK, but you still had the pull request URL in the cover letter, so I
tried it. Anyway, not a big deal as far as that goes.
> >
> > I can grab these out of patchworks, but even that way I still need
> > you
> > to be clear about what tree/branch these are intended to be applied
> > to.
>
> It should apply cleanly as patches grabbed from the patchworks and if
> for any reasons it doesn't work for you, please drop it and I'll
> resubmit.
Apply cleanly where? That was the other part of my email. When you
have a shared pull request, and it isn't based on my for-next branch
(as this one isn't), please let me know in each patch series whether
you intend it to be applied on the shared pull request or my for-next
branch.
I actually applied it to the shared pull request branch, but I didn't
know if that's what you had intended. Also, I rewrote the commit
message in patch 5/6 entirely. But, otherwise, thanks, applied.
--
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-10-18 16:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 5:45 [PATCH rdma-next v1 0/6] RDMA core and mlx5 fixes and refactoring for 4.15 Leon Romanovsky
[not found] ` <20171016054517.30643-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-10-16 5:45 ` [PATCH rdma-next v1 1/6] IB/core: Introduce and use rdma_create_user_ah Leon Romanovsky
2017-10-16 5:45 ` [PATCH rdma-next v1 2/6] IB: Let ib_core resolve destination mac address Leon Romanovsky
2017-10-16 5:45 ` [PATCH rdma-next v1 3/6] IB/core: Fix unable to change lifespan entry for hw_counters Leon Romanovsky
2017-10-16 5:45 ` [PATCH rdma-next v1 4/6] IB/core: Fix use workqueue without WQ_MEM_RECLAIM Leon Romanovsky
[not found] ` <20171016054517.30643-5-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-10-16 17:24 ` Jonathan Toppins
[not found] ` <4f08314e-fd5d-c108-438a-d9e83821e4b3-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-10-16 18:32 ` Leon Romanovsky
2017-10-18 9:58 ` Sagi Grimberg
[not found] ` <3c717580-d1fe-943d-8df2-5d4858244e9b-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
2017-10-18 14:21 ` Leon Romanovsky
2017-10-16 5:45 ` [PATCH rdma-next v1 5/6] IB/core: Take into account optional UDR, XRC headers and mandatory ICRC for RoCE MTU Leon Romanovsky
[not found] ` <20171016054517.30643-6-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-10-17 11:12 ` Leon Romanovsky
[not found] ` <20171017111228.GO2106-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-10-18 15:13 ` Doug Ledford
2017-10-16 5:45 ` [PATCH rdma-next v1 6/6] IB/mlx5: Use ARRAY_SIZE Leon Romanovsky
2017-10-18 15:25 ` [PATCH rdma-next v1 0/6] RDMA core and mlx5 fixes and refactoring for 4.15 Doug Ledford
[not found] ` <1508340309.46071.76.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-10-18 15:40 ` Leon Romanovsky
[not found] ` <20171018154006.GS2106-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-10-18 16:20 ` Doug Ledford [this message]
[not found] ` <1508343627.2951.4.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-10-18 16:35 ` Parav Pandit
2017-10-18 20:41 ` Leon Romanovsky
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=1508343627.2951.4.camel@redhat.com \
--to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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.