From: Sean Anderson <sean.anderson@seco.com>
To: Yuan Can <yuancan@huawei.com>,
leoyang.li@nxp.com, davem@davemloft.net, camelia.groza@nxp.com,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] soc: fsl: qbman: Remove unused struct cgr_comp
Date: Tue, 27 Sep 2022 11:48:48 -0400 [thread overview]
Message-ID: <b3decabe-94d4-2bb3-0926-e4c4a6d66c60@seco.com> (raw)
In-Reply-To: <20220927133628.97774-1-yuancan@huawei.com>
On 9/27/22 9:36 AM, Yuan Can wrote:
> [You don't often get email from yuancan@huawei.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> After commit 96f413f47677("soc/fsl/qbman: fix issue in qman_delete_cgr_safe()"),
> no one use struct cgr_comp, so remove it.
>
> Signed-off-by: Yuan Can <yuancan@huawei.com>
> ---
> drivers/soc/fsl/qbman/qman.c | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/drivers/soc/fsl/qbman/qman.c b/drivers/soc/fsl/qbman/qman.c
> index 739e4eee6b75..4cebfe7f663b 100644
> --- a/drivers/soc/fsl/qbman/qman.c
> +++ b/drivers/soc/fsl/qbman/qman.c
> @@ -2543,11 +2543,6 @@ int qman_delete_cgr(struct qman_cgr *cgr)
> }
> EXPORT_SYMBOL(qman_delete_cgr);
>
> -struct cgr_comp {
> - struct qman_cgr *cgr;
> - struct completion completion;
> -};
> -
> static void qman_delete_cgr_smp_call(void *p)
> {
> qman_delete_cgr((struct qman_cgr *)p);
> --
> 2.17.1
>
Reviewed-by: Sean Anderson <sean.anderson@seco.com>
prev parent reply other threads:[~2022-09-27 15:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 13:36 [PATCH] soc: fsl: qbman: Remove unused struct cgr_comp Yuan Can
2022-09-27 15:48 ` Sean Anderson [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=b3decabe-94d4-2bb3-0926-e4c4a6d66c60@seco.com \
--to=sean.anderson@seco.com \
--cc=camelia.groza@nxp.com \
--cc=davem@davemloft.net \
--cc=leoyang.li@nxp.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=yuancan@huawei.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).