From: David Miller <davem@davemloft.net>
To: horatiu.vultur@microchip.com
Cc: alexandre.belloni@bootlin.com, UNGLinuxDriver@microchip.com,
robh+dt@kernel.org, mark.rutland@arm.com, ralf@linux-mips.org,
paul.burton@mips.com, jhogan@kernel.org,
linux-mips@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/2] Add hw offload of TC flower on MSCC Ocelot
Date: Sun, 02 Jun 2019 13:50:10 -0700 (PDT) [thread overview]
Message-ID: <20190602.135010.1382762534390460032.davem@davemloft.net> (raw)
In-Reply-To: <1559287017-32397-1-git-send-email-horatiu.vultur@microchip.com>
From: Horatiu Vultur <horatiu.vultur@microchip.com>
Date: Fri, 31 May 2019 09:16:55 +0200
> This patch series enables hardware offload for flower filter used in
> traffic controller on MSCC Ocelot board.
>
> v2->v3 changes:
> - remove the check for shared blocks
>
> v1->v2 changes:
> - when declaring variables use reverse christmas tree
Series applied, thanks.
prev parent reply other threads:[~2019-06-02 20:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 7:16 [PATCH net-next v3 0/2] Add hw offload of TC flower on MSCC Ocelot Horatiu Vultur
2019-05-31 7:16 ` [PATCH net-next v3 1/2] net: mscc: ocelot: Add support for tcam Horatiu Vultur
2020-02-24 10:38 ` Vladimir Oltean
2020-02-24 11:03 ` Horatiu Vultur
2020-02-24 11:32 ` Vladimir Oltean
2020-04-22 21:26 ` Vladimir Oltean
2020-04-23 8:29 ` Horatiu Vultur
2020-04-23 9:18 ` Vladimir Oltean
2020-09-24 23:39 ` Vladimir Oltean
2020-09-26 11:20 ` Horatiu Vultur
2020-09-26 12:37 ` Vladimir Oltean
2020-09-26 18:55 ` Horatiu Vultur
2020-09-26 19:06 ` Vladimir Oltean
2019-05-31 7:16 ` [PATCH net-next v3 2/2] net: mscc: ocelot: Hardware ofload for tc flower filter Horatiu Vultur
2019-06-02 20:50 ` 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=20190602.135010.1382762534390460032.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=horatiu.vultur@microchip.com \
--cc=jhogan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=paul.burton@mips.com \
--cc=ralf@linux-mips.org \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).