From: Yuval Shaia <yuval.shaia-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Jason Gunthorpe <jgg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
RDMA mailing list
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH rdma-next] RDMA/mlx5; Remove redundant allocation warning print
Date: Fri, 19 Jan 2018 20:54:28 +0200 [thread overview]
Message-ID: <20180119185427.GB2624@yuvallap> (raw)
In-Reply-To: <20180119105840.GA1393-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
> > >
> > > Fixes: d69a24e03659 ("IB/mlx5: Move IB event processing onto a workqueue")
> >
> > Didn't found it in:
> > https://kernel.googlesource.com/pub/scm/linux/kernel/git/leon/linux-rdma/
> > branch rdma-next and didn't find it.
> > Where should i look?
>
> In official place:
> https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git/commit/?h=for-next&id=d69a24e036596877ce08c25ab8e63a202412fd9e
I see,
I thought that "rdma-next" in subject stands for branch name, apparently
not. So saying rdma-next you actually refer to for-next, right?
>
> >
--
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:[~2018-01-19 18:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 12:34 [PATCH rdma-next] RDMA/mlx5; Remove redundant allocation warning print Leon Romanovsky
[not found] ` <20180118123424.21062-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2018-01-18 20:02 ` Yuval Shaia
2018-01-19 10:58 ` Leon Romanovsky
[not found] ` <20180119105840.GA1393-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2018-01-19 18:54 ` Yuval Shaia [this message]
2018-01-21 13: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=20180119185427.GB2624@yuvallap \
--to=yuval.shaia-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=jgg-VPRAkNaXOzVWk0Htik3J/w@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.