From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Or Gerlitz <gerlitz.or-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Haggai Eran <haggaie-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 0/2] lockdep warning fixes
Date: Thu, 09 Jul 2015 09:17:23 -0400 [thread overview]
Message-ID: <559E7463.6070709@redhat.com> (raw)
In-Reply-To: <CAJ3xEMiydOEN_baOJcdcH0=LL+6Qv2HM5XJGirjqFHfz4zif5g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1747 bytes --]
On 07/09/2015 06:49 AM, Or Gerlitz wrote:
> On Thu, Jul 9, 2015 at 1:36 AM, Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
>> Thanks, both applied.
>
> to where?!
To my tree. The fact that I've taken it in does not mean I have pushed
the tree out yet. The set of rc fixes has not yet passed my build/run
tests. I'll push the tree out when it has.
> Doug, I didn't see any update on your gitbub nor your
> kernel.org tree,
Because it hasn't been pushed yet.
> and again, it's a bit annoying to chase two trees w.o
> clear branching policy...
The trees already have a clear branching policy.
> can you use something with clear name (say)
> 4.2-fixes on your github and it would be clear that 4.2 rc fixes go
> there?
When I push it, it will be obvious.
> Also, I didn't see a note from you on picking the fixes from Ira and
> myself to address the comments from Linus..
I haven't worked through all of the patches yet. Nor have I notified
everyone about every patch. However, a few of the patches I lost the
original email to and so they won't get a response. When I push the
tree though, you can check that the patches you care about are present.
> Ira's https://patchwork.kernel.org/patch/6675271/ -- this still has
> blank line that I asked Ira to remove, so if you can either ask him to
> do so, or clean this up yourself...
>
> mine https://patchwork.kernel.org/patch/6675921/
>
> and the mlx4 fix Matan's code plus the ipoib fix
>
> https://patchwork.kernel.org/patch/6702851/
> https://patchwork.kernel.org/patch/6702841/
>
>
> Or.
>
--
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
GPG KeyID: 0E572FDD
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]
prev parent reply other threads:[~2015-07-09 13:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 14:45 [PATCH 0/2] lockdep warning fixes Haggai Eran
[not found] ` <1436280313-21451-1-git-send-email-haggaie-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2015-07-07 14:45 ` [PATCH 1/2] IB/ucma: Fix lockdep warning in ucma_lock_files Haggai Eran
2015-07-07 14:45 ` [PATCH 2/2] IB/ipoib: Prevent lockdep warning in __ipoib_ib_dev_flush Haggai Eran
2015-07-08 22:36 ` [PATCH 0/2] lockdep warning fixes Doug Ledford
[not found] ` <559DA5E9.5050500-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-07-09 10:49 ` Or Gerlitz
[not found] ` <CAJ3xEMiydOEN_baOJcdcH0=LL+6Qv2HM5XJGirjqFHfz4zif5g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-07-09 13:17 ` Doug Ledford [this message]
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=559E7463.6070709@redhat.com \
--to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=gerlitz.or-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=haggaie-VPRAkNaXOzVWk0Htik3J/w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox