From: Saeed Mahameed <saeedm@mellanox.com>
To: "dan.carpenter@oracle.com" <dan.carpenter@oracle.com>,
"leon@kernel.org" <leon@kernel.org>
Cc: Vu Pham <vuhuong@mellanox.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH] net/mlx5: E-Switch, Fix some error pointer dereferences
Date: Thu, 11 Jun 2020 22:06:20 +0000 [thread overview]
Message-ID: <fcac5706683cc63cfd2db520e53826e604f59ae3.camel@mellanox.com> (raw)
In-Reply-To: <20200608133109.GQ22511@kadam>
On Mon, 2020-06-08 at 16:31 +0300, Dan Carpenter wrote:
> On Sun, Jun 07, 2020 at 09:25:55AM +0300, Leon Romanovsky wrote:
> > On Fri, Jun 05, 2020 at 01:52:03PM +0300, Dan Carpenter wrote:
> > > On Thu, Jun 04, 2020 at 01:32:55PM +0300, Leon Romanovsky wrote:
> > > > + netdev
> > > >
> > >
> > > This is sort of useless. What's netdev going to do with a patch
> > > they
> > > can't apply? I assumed that mellanox was going to take this
> > > through
> > > their tree...
> >
> > Right, but it will be picked by Saeed who will send it to netdev
> > later
> > as PR. CCing netdev saves extra review at that stage.
>
> Okay. I will try to remember this in the future. I'll try put
> [PATCH mlx5-next] in the subject even when it applies to the net
> tree.
Thanks Dan for the patch.
netdev is always open for fixes.
Applied to net-mlx5, will send this in today PR to net.
-Saeed.
>
> regards,
> dan carpenter
>
prev parent reply other threads:[~2020-06-11 22:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200603175436.GD18931@mwanda>
2020-06-04 10:32 ` [PATCH] net/mlx5: E-Switch, Fix some error pointer dereferences Leon Romanovsky
2020-06-05 10:52 ` Dan Carpenter
2020-06-07 6:25 ` Leon Romanovsky
2020-06-08 13:31 ` Dan Carpenter
2020-06-11 22:06 ` Saeed Mahameed [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=fcac5706683cc63cfd2db520e53826e604f59ae3.camel@mellanox.com \
--to=saeedm@mellanox.com \
--cc=dan.carpenter@oracle.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vuhuong@mellanox.com \
/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;
as well as URLs for NNTP newsgroup(s).