From: Pkshih <pkshih@realtek.com>
To: "joe@perches.com" <joe@perches.com>,
"kvalo@kernel.org" <kvalo@kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] rtw89: rtw89_ser: add const to struct state_ent and event_ent
Date: Fri, 8 Apr 2022 00:16:44 +0000 [thread overview]
Message-ID: <9455b32da137028a5c0d6dd010a247094d19309a.camel@realtek.com> (raw)
In-Reply-To: <2fd88e6119f62b968477ef9781abb1832d399fd6.camel@perches.com>
On Thu, 2022-04-07 at 13:14 -0700, Joe Perches wrote:
> Change the struct and the uses to const to reduce data.
>
> $ size drivers/net/wireless/realtek/rtw89/ser.o* (x86-64 defconfig w/ rtw89)
> text data bss dec hex filename
> 3741 8 0 3749 ea5 drivers/net/wireless/realtek/rtw89/ser.o.new
> 3437 312 0 3749 ea5 drivers/net/wireless/realtek/rtw89/ser.o.old
>
> Signed-off-by: Joe Perches <joe@perches.com>
Acked-by: Ping-Ke Shih <pkshih@realtek.com>
Thank you.
> ---
> drivers/net/wireless/realtek/rtw89/core.h | 4 ++--
> drivers/net/wireless/realtek/rtw89/ser.c | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/net/wireless/realtek/rtw89/core.h b/drivers/net/wireless/realtek/rtw89/core.h
> index 771722132c53b..9bf56ce5ab43f 100644
> --- a/drivers/net/wireless/realtek/rtw89/core.h
> +++ b/drivers/net/wireless/realtek/rtw89/core.h
> @@ -2853,8 +2853,8 @@ struct rtw89_ser {
>
> struct work_struct ser_hdl_work;
> struct delayed_work ser_alarm_work;
> - struct state_ent *st_tbl;
> - struct event_ent *ev_tbl;
> + const struct state_ent *st_tbl;
> + const struct event_ent *ev_tbl;
> struct list_head msg_q;
> spinlock_t msg_q_lock; /* lock when read/write ser msg */
> DECLARE_BITMAP(flags, RTW89_NUM_OF_SER_FLAGS);
> diff --git a/drivers/net/wireless/realtek/rtw89/ser.c b/drivers/net/wireless/realtek/rtw89/ser.c
> index 837cdc366a61a..7fbda7ef96bbb 100644
> --- a/drivers/net/wireless/realtek/rtw89/ser.c
> +++ b/drivers/net/wireless/realtek/rtw89/ser.c
> @@ -396,7 +396,7 @@ static void ser_l2_reset_st_hdl(struct rtw89_ser *ser, u8 evt)
> }
> }
>
> -static struct event_ent ser_ev_tbl[] = {
> +static const struct event_ent ser_ev_tbl[] = {
> {SER_EV_NONE, "SER_EV_NONE"},
> {SER_EV_STATE_IN, "SER_EV_STATE_IN"},
> {SER_EV_STATE_OUT, "SER_EV_STATE_OUT"},
> @@ -412,7 +412,7 @@ static struct event_ent ser_ev_tbl[] = {
> {SER_EV_MAXX, "SER_EV_MAX"}
> };
>
> -static struct state_ent ser_st_tbl[] = {
> +static const struct state_ent ser_st_tbl[] = {
> {SER_IDLE_ST, "SER_IDLE_ST", ser_idle_st_hdl},
> {SER_RESET_TRX_ST, "SER_RESET_TRX_ST", ser_reset_trx_st_hdl},
> {SER_DO_HCI_ST, "SER_DO_HCI_ST", ser_do_hci_st_hdl},
>
>
> ------Please consider the environment before printing this e-mail.
next prev parent reply other threads:[~2022-04-08 0:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 20:14 Joe Perches
2022-04-08 0:16 ` Pkshih [this message]
2022-04-12 13:37 ` Kalle Valo
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=9455b32da137028a5c0d6dd010a247094d19309a.camel@realtek.com \
--to=pkshih@realtek.com \
--cc=davem@davemloft.net \
--cc=joe@perches.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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
all inboxes | Powered by JetHome®