All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: netdev@vger.kernel.org, kuba@kernel.org, davem@davemloft.net,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] net: apple: bmac: Fix build since dev_addr constification
Date: Fri, 14 Jan 2022 11:30:10 +0000	[thread overview]
Message-ID: <164215981049.30922.9359003030904189013.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220114031316.2419293-1-mpe@ellerman.id.au>

Hello:

This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:

On Fri, 14 Jan 2022 14:13:16 +1100 you wrote:
> Since commit adeef3e32146 ("net: constify netdev->dev_addr") the bmac
> driver no longer builds with the following errors (pmac32_defconfig):
> 
>   linux/drivers/net/ethernet/apple/bmac.c: In function ‘bmac_probe’:
>   linux/drivers/net/ethernet/apple/bmac.c:1287:20: error: assignment of read-only location ‘*(dev->dev_addr + (sizetype)j)’
>    1287 |   dev->dev_addr[j] = rev ? bitrev8(addr[j]): addr[j];
>         |                    ^
> 
> [...]

Here is the summary with links:
  - net: apple: bmac: Fix build since dev_addr constification
    https://git.kernel.org/netdev/net/c/ea938248557a

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: netdev@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	davem@davemloft.net, kuba@kernel.org
Subject: Re: [PATCH] net: apple: bmac: Fix build since dev_addr constification
Date: Fri, 14 Jan 2022 11:30:10 +0000	[thread overview]
Message-ID: <164215981049.30922.9359003030904189013.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220114031316.2419293-1-mpe@ellerman.id.au>

Hello:

This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:

On Fri, 14 Jan 2022 14:13:16 +1100 you wrote:
> Since commit adeef3e32146 ("net: constify netdev->dev_addr") the bmac
> driver no longer builds with the following errors (pmac32_defconfig):
> 
>   linux/drivers/net/ethernet/apple/bmac.c: In function ‘bmac_probe’:
>   linux/drivers/net/ethernet/apple/bmac.c:1287:20: error: assignment of read-only location ‘*(dev->dev_addr + (sizetype)j)’
>    1287 |   dev->dev_addr[j] = rev ? bitrev8(addr[j]): addr[j];
>         |                    ^
> 
> [...]

Here is the summary with links:
  - net: apple: bmac: Fix build since dev_addr constification
    https://git.kernel.org/netdev/net/c/ea938248557a

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2022-01-14 11:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-14  3:13 [PATCH] net: apple: bmac: Fix build since dev_addr constification Michael Ellerman
2022-01-14  3:13 ` Michael Ellerman
2022-01-14  4:21 ` Jakub Kicinski
2022-01-14  4:21   ` Jakub Kicinski
2022-01-14 11:30 ` patchwork-bot+netdevbpf [this message]
2022-01-14 11:30   ` patchwork-bot+netdevbpf

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=164215981049.30922.9359003030904189013.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=netdev@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.