From: Jakub Kicinski <kuba@kernel.org>
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: Rob Herring <robh+dt@kernel.org>, Tero Kristo <t-kristo@ti.com>,
"David S . Miller" <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>, Roger Quadros <rogerq@ti.com>,
<devicetree@vger.kernel.org>,
Murali Karicheri <m-karicheri2@ti.com>,
Sekhar Nori <nsekhar@ti.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH net-next v3 05/10] net: ethernet: ti: introduce am65x/j721e gigabit eth subsystem driver
Date: Fri, 13 Mar 2020 13:04:38 -0700 [thread overview]
Message-ID: <20200313130438.73d9a56c@kicinski-fedora-PC1C0HJN> (raw)
In-Reply-To: <20200313175511.2155-6-grygorii.strashko@ti.com>
On Fri, 13 Mar 2020 19:55:06 +0200 Grygorii Strashko wrote:
> +static void am65_cpsw_nuss_free_tx_chns(void *data)
> +{
> + struct am65_cpsw_common *common = data;
> + int i;
> +
> + for (i = 0; i < common->tx_ch_num; i++) {
> + struct am65_cpsw_tx_chn *tx_chn = &common->tx_chns[i];
nit: stray tab?
> +
> + if (!IS_ERR_OR_NULL(tx_chn->tx_chn))
> + k3_udma_glue_release_tx_chn(tx_chn->tx_chn);
> +
> + if (!IS_ERR_OR_NULL(tx_chn->desc_pool))
> + k3_udma_desc_pool_destroy(tx_chn->desc_pool);
> +
> + memset(tx_chn, 0, sizeof(*tx_chn));
> + };
nit: you also got some stray semicolons in a few places
Thanks for the changes, looks better. Hopefully someone who knows
the HW better can have a look as well.
next prev parent reply other threads:[~2020-03-13 20:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 17:55 [PATCH net-next v3 00/10] net: ethernet: ti: add networking support for k3 am65x/j721e soc Grygorii Strashko
2020-03-13 17:55 ` [PATCH net-next v3 01/10] net: ethernet: ti: ale: fix seeing unreg mcast packets with promisc and allmulti disabled Grygorii Strashko
2020-03-13 17:55 ` [PATCH net-next v3 02/10] net: ethernet: ti: ale: add support for mac-only mode Grygorii Strashko
2020-03-13 17:55 ` [PATCH net-next v3 03/10] net: ethernet: ti: ale: am65: add support for default thread cfg Grygorii Strashko
2020-03-13 17:55 ` [PATCH net-next v3 04/10] dt-binding: ti: am65x: document mcu cpsw nuss Grygorii Strashko
2020-03-13 17:55 ` [PATCH net-next v3 05/10] net: ethernet: ti: introduce am65x/j721e gigabit eth subsystem driver Grygorii Strashko
2020-03-13 20:04 ` Jakub Kicinski [this message]
2020-03-13 17:55 ` [PATCH net-next v3 06/10] arm64: dts: ti: k3-am65-mcu: add cpsw nuss node Grygorii Strashko
2020-03-13 17:55 ` [PATCH net-next v3 07/10] arm64: dts: k3-am654-base-board: add mcu cpsw nuss pinmux and phy defs Grygorii Strashko
2020-03-13 17:55 ` [PATCH net-next v3 08/10] arm64: dts: ti: k3-j721e-mcu: add mcu cpsw nuss node Grygorii Strashko
2020-03-13 17:55 ` [PATCH net-next v3 09/10] arm64: dts: ti: k3-j721e-common-proc-board: add mcu cpsw nuss pinmux and phy defs Grygorii Strashko
2020-03-13 17:55 ` [PATCH net-next v3 10/10] arm64: defconfig: ti: k3: enable dma and networking Grygorii Strashko
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=20200313130438.73d9a56c@kicinski-fedora-PC1C0HJN \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-karicheri2@ti.com \
--cc=netdev@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=robh+dt@kernel.org \
--cc=rogerq@ti.com \
--cc=t-kristo@ti.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).