public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Philipp Hortmann <philipp.g.hortmann@gmail.com>
Cc: Forest Bond <forest@alittletooquiet.net>,
	Joe Perches <joe@perches.com>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] staging: vt6655: Use loop in vt6655_mac_write_bssid_addr
Date: Fri, 8 Jul 2022 14:29:44 +0200	[thread overview]
Message-ID: <YsgjOPUDDtD48tMO@kroah.com> (raw)
In-Reply-To: <b3b93ae7ce41562565e9007eb4580b9c47a2881f.1657134099.git.philipp.g.hortmann@gmail.com>

On Wed, Jul 06, 2022 at 09:19:01PM +0200, Philipp Hortmann wrote:
> Use loop in vt6655_mac_write_bssid_addr to avoid multiple
> similar statements.
> 
> Signed-off-by: Philipp Hortmann <philipp.g.hortmann@gmail.com>
> ---
> Code for testing:
> for (int i = 0; i < 6; i++){
> 	iowrite8(mac_addr[i], iobase + MAC_REG_BSSID0 + i);
> 	printk("i = %i\n", i);
> }
> 
> Log:
> [ 2592.189081] i = 0
> [ 2592.189083] i = 1
> [ 2592.189083] i = 2
> [ 2592.189084] i = 3
> [ 2592.189084] i = 4
> [ 2592.189085] i = 5
> ---
>  drivers/staging/vt6655/device_main.c | 8 ++------
>  1 file changed, 2 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/staging/vt6655/device_main.c b/drivers/staging/vt6655/device_main.c
> index 298963cbca1d..099f0b95417a 100644
> --- a/drivers/staging/vt6655/device_main.c
> +++ b/drivers/staging/vt6655/device_main.c
> @@ -192,12 +192,8 @@ device_set_options(struct vnt_private *priv)
>  static void vt6655_mac_write_bssid_addr(void __iomem *iobase, const u8 *mac_addr)
>  {
>  	iowrite8(1, iobase + MAC_REG_PAGE1SEL);
> -	iowrite8(mac_addr[0], iobase + MAC_REG_BSSID0);
> -	iowrite8(mac_addr[1], iobase + MAC_REG_BSSID0 + 1);
> -	iowrite8(mac_addr[2], iobase + MAC_REG_BSSID0 + 2);
> -	iowrite8(mac_addr[3], iobase + MAC_REG_BSSID0 + 3);
> -	iowrite8(mac_addr[4], iobase + MAC_REG_BSSID0 + 4);
> -	iowrite8(mac_addr[5], iobase + MAC_REG_BSSID0 + 5);
> +	for (int i = 0; i < 6; i++)

Taking advantage of the new compiler level I see, nice :)


  reply	other threads:[~2022-07-08 12:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-06 19:18 [PATCH 0/2] staging: vt6655: Reduce similar statements when working with mac addr Philipp Hortmann
2022-07-06 19:19 ` [PATCH 1/2] staging: vt6655: Use loop in vt6655_mac_write_bssid_addr Philipp Hortmann
2022-07-08 12:29   ` Greg Kroah-Hartman [this message]
2022-07-09  4:07     ` Joe Perches
2022-07-09  7:02       ` Greg Kroah-Hartman
2022-07-06 19:19 ` [PATCH 2/2] staging: vt6655: Use loop in vt6655_mac_read_ether_addr Philipp Hortmann

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=YsgjOPUDDtD48tMO@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=forest@alittletooquiet.net \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=philipp.g.hortmann@gmail.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