From: David Miller <davem@davemloft.net>
To: gerlitz.or@gmail.com
Cc: xiangxia.m.yue@gmail.com, netdev@vger.kernel.org,
hadarh@mellanox.com, saeedm@mellanox.com
Subject: Re: [PATCH net v5 1/2] net/mlx5e: Update hw flows when encap source mac changed
Date: Wed, 06 Feb 2019 17:11:45 -0800 (PST) [thread overview]
Message-ID: <20190206.171145.661038744264162576.davem@davemloft.net> (raw)
In-Reply-To: <CAJ3xEMgb0MnO8O2_0cQQkjmwe2PcjXb5PeOexRPfejpsyX98zg@mail.gmail.com>
From: Or Gerlitz <gerlitz.or@gmail.com>
Date: Tue, 5 Feb 2019 11:03:01 +0200
> Dave, I see a copy of the patch on patchworks [1] with status being
> not applicable, what is missing here? the patch should apply AFAIK.
> There was also another patch reviewed here by me and Saeed [2], not
> sure where it stands from your side.
>
> [1] https://patchwork.ozlabs.org/patch/1023844/
> [2] https://marc.info/?l=linux-netdev&m=154878514916414&w=2
More precisely, it's marked "Awaiting Upstream" which means I for some reason
expected Saeed to send it to me in his next pull request.
I'll apply these now.
prev parent reply other threads:[~2019-02-07 1:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 23:28 [PATCH net v5 1/2] net/mlx5e: Update hw flows when encap source mac changed xiangxia.m.yue
2019-01-28 23:28 ` [PATCH net v5 2/2] net/mlx5e: Don't overwrite pedit action when multiple pedit used xiangxia.m.yue
2019-01-29 20:17 ` Or Gerlitz
2019-01-29 22:21 ` Saeed Mahameed
2019-01-29 20:16 ` [PATCH net v5 1/2] net/mlx5e: Update hw flows when encap source mac changed Or Gerlitz
2019-01-29 22:20 ` Saeed Mahameed
2019-02-05 9:03 ` Or Gerlitz
2019-02-07 1:11 ` David Miller [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=20190206.171145.661038744264162576.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=gerlitz.or@gmail.com \
--cc=hadarh@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.com \
--cc=xiangxia.m.yue@gmail.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