public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel•org
To: Randy Dunlap <rdunlap@infradead•org>
Cc: netdev@vger•kernel.org, geert@linux-m68k•org,
	richard.cochran@omicron•at, john.stultz@linaro•org,
	davem@davemloft•net, kuba@kernel•org, andrew@lunn•ch,
	hkallweit1@gmail•com, linux@armlinux•org.uk
Subject: Re: [PATCH -net] ptp: dp83640: don't define PAGE0
Date: Wed, 15 Sep 2021 03:10:06 +0000	[thread overview]
Message-ID: <163167540674.9269.1991816632448031713.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210913220605.19682-1-rdunlap@infradead.org>

Hello:

This patch was applied to netdev/net.git (refs/heads/master):

On Mon, 13 Sep 2021 15:06:05 -0700 you wrote:
> Building dp83640.c on arch/parisc/ produces a build warning for
> PAGE0 being redefined. Since the macro is not used in the dp83640
> driver, just make it a comment for documentation purposes.
> 
> In file included from ../drivers/net/phy/dp83640.c:23:
> ../drivers/net/phy/dp83640_reg.h:8: warning: "PAGE0" redefined
>     8 | #define PAGE0                     0x0000
>                  from ../drivers/net/phy/dp83640.c:11:
> ../arch/parisc/include/asm/page.h:187: note: this is the location of the previous definition
>   187 | #define PAGE0   ((struct zeropage *)__PAGE_OFFSET)
> 
> [...]

Here is the summary with links:
  - [-net] ptp: dp83640: don't define PAGE0
    https://git.kernel.org/netdev/net/c/7366c23ff492

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



      parent reply	other threads:[~2021-09-15  3:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-13 22:06 [PATCH -net] ptp: dp83640: don't define PAGE0 Randy Dunlap
2021-09-14  0:24 ` Andrew Lunn
2021-09-15  3:10 ` patchwork-bot+netdevbpf [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=163167540674.9269.1991816632448031713.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel$(echo .)org \
    --cc=andrew@lunn$(echo .)ch \
    --cc=davem@davemloft$(echo .)net \
    --cc=geert@linux-m68k$(echo .)org \
    --cc=hkallweit1@gmail$(echo .)com \
    --cc=john.stultz@linaro$(echo .)org \
    --cc=kuba@kernel$(echo .)org \
    --cc=linux@armlinux$(echo .)org.uk \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=rdunlap@infradead$(echo .)org \
    --cc=richard.cochran@omicron$(echo .)at \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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