All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yongqiang Liu <liuyongqiang13@huawei.com>
To: <f.fainelli@gmail.com>, <bcm-kernel-feedback-list@broadcom.com>
Cc: <linux-arm-kernel@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH -next] soc: bcm: brcmstb: Remove unused variable brcmstb_machine_match.
Date: Thu, 3 Jun 2021 02:44:26 +0000	[thread overview]
Message-ID: <20210603024426.1124761-1-liuyongqiang13@huawei.com> (raw)

Since commit 8b8f095b9076 ("soc: bcm: brcmstb: Remove soc_is_brcmstb()")
remove the function soc_is_brcmstb(), the global variable
brcmstb_machine_match is no longer useful. So remove it.

Signed-off-by: Yongqiang Liu <liuyongqiang13@huawei.com>
---
 drivers/soc/bcm/brcmstb/common.c | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/drivers/soc/bcm/brcmstb/common.c b/drivers/soc/bcm/brcmstb/common.c
index e87dfc6660f3..2a010881f4b6 100644
--- a/drivers/soc/bcm/brcmstb/common.c
+++ b/drivers/soc/bcm/brcmstb/common.c
@@ -14,11 +14,6 @@
 static u32 family_id;
 static u32 product_id;
 
-static const struct of_device_id brcmstb_machine_match[] = {
-	{ .compatible = "brcm,brcmstb", },
-	{ }
-};
-
 u32 brcmstb_get_family_id(void)
 {
 	return family_id;
-- 
2.19.1


WARNING: multiple messages have this Message-ID (diff)
From: Yongqiang Liu <liuyongqiang13@huawei.com>
To: <f.fainelli@gmail.com>, <bcm-kernel-feedback-list@broadcom.com>
Cc: <linux-arm-kernel@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH -next] soc: bcm: brcmstb: Remove unused variable brcmstb_machine_match.
Date: Thu, 3 Jun 2021 02:44:26 +0000	[thread overview]
Message-ID: <20210603024426.1124761-1-liuyongqiang13@huawei.com> (raw)

Since commit 8b8f095b9076 ("soc: bcm: brcmstb: Remove soc_is_brcmstb()")
remove the function soc_is_brcmstb(), the global variable
brcmstb_machine_match is no longer useful. So remove it.

Signed-off-by: Yongqiang Liu <liuyongqiang13@huawei.com>
---
 drivers/soc/bcm/brcmstb/common.c | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/drivers/soc/bcm/brcmstb/common.c b/drivers/soc/bcm/brcmstb/common.c
index e87dfc6660f3..2a010881f4b6 100644
--- a/drivers/soc/bcm/brcmstb/common.c
+++ b/drivers/soc/bcm/brcmstb/common.c
@@ -14,11 +14,6 @@
 static u32 family_id;
 static u32 product_id;
 
-static const struct of_device_id brcmstb_machine_match[] = {
-	{ .compatible = "brcm,brcmstb", },
-	{ }
-};
-
 u32 brcmstb_get_family_id(void)
 {
 	return family_id;
-- 
2.19.1


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2021-06-03  2:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03  2:44 Yongqiang Liu [this message]
2021-06-03  2:44 ` [PATCH -next] soc: bcm: brcmstb: Remove unused variable brcmstb_machine_match Yongqiang Liu
2021-06-04 17:53 ` Florian Fainelli
2021-06-04 17:53   ` Florian Fainelli

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=20210603024426.1124761-1-liuyongqiang13@huawei.com \
    --to=liuyongqiang13@huawei.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=f.fainelli@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.