public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Mike Looijmans <mike.looijmans@topic.nl>
Cc: David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, f.fainelli@gmail.com,
	robh+dt@kernel.org, frowand.list@gmail.com
Subject: Re: [PATCH v4 0/2] of_net: Implement of_get_nvmem_mac_address helper
Date: Sat, 31 Mar 2018 19:27:35 +0200	[thread overview]
Message-ID: <20180331172735.GC7460@lunn.ch> (raw)
In-Reply-To: <56a0d45c-bf2a-0d9a-fa2e-9f6531caa61c@topic.nl>

On Sat, Mar 31, 2018 at 07:20:30PM +0200, Mike Looijmans wrote:
> On 30-03-18 16:40, David Miller wrote:
> >From: Mike Looijmans <mike.looijmans@topic.nl>
> >Date: Thu, 29 Mar 2018 07:29:47 +0200
> >
> >>Posted this as a small set now, with an (optional) second patch that shows
> >>how the changes work and what I've used to test the code on a Topic Miami board.
> >>I've taken the liberty to add appropriate "Acked" and "Review" tags.
> >>
> >>v4: Replaced "6" with ETH_ALEN
> >>
> >>v3: Add patch that implements mac in nvmem for the Cadence MACB controller
> >>     Remove the integrated of_get_mac_address call
> >>
> >>v2: Use of_nvmem_cell_get to avoid needing the assiciated device
> >>     Use void* instead of char*
> >>     Add devicetree binding doc
> >
> >Series applied to net-next, thank you.
> >
> 
> Got a kbuild bot error message in the e-mail, with errors like: "undefined
> reference to `of_nvmem_cell_get'"
> 
> Should I add an "#if CONFIG_NVMEM" guard around the new code and make a v5
> patch?

Hi Mike

You need to understand what is actually causing the problem. If it no
NVMEM, or no OF? The kernel config was part of the email, so you
should be able to reproduce the failure.

We don't normally add #ifdef in code. Instead we implement stub
functions in the header file, which would in this case return
something like -ENODEV.

Dave has already take this patch. So you need to do an incremental
fix.

	  Andrew

      reply	other threads:[~2018-03-31 17:27 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-23 14:24 [PATCH] of_net: Implement of_get_nvmem_mac_address helper Mike Looijmans
2018-03-23 15:11 ` Andrew Lunn
2018-03-23 19:20   ` Mike Looijmans
2018-03-23 19:33     ` Florian Fainelli
2018-03-24 16:17       ` Mike Looijmans
2018-03-24 18:53         ` Andrew Lunn
2018-03-25  8:17           ` Mike Looijmans
2018-03-25 21:04             ` Andrew Lunn
2018-03-26  6:54             ` Mike Looijmans
2018-03-23 19:42     ` Andrew Lunn
2018-03-24 16:03       ` Mike Looijmans
2018-03-26  6:41 ` [PATCH v2] " Mike Looijmans
2018-03-26 15:50   ` Andrew Lunn
2018-03-26 18:25     ` Mike Looijmans
2018-03-26 18:41       ` Andrew Lunn
2018-03-26 16:58   ` David Miller
2018-03-26 17:05     ` Florian Fainelli
2018-03-26 18:21       ` Mike Looijmans
2018-03-27  9:52   ` [PATCH v3 0/2] " Mike Looijmans
2018-03-27  9:52     ` [PATCH v3 1/2] " Mike Looijmans
2018-03-27 22:50       ` Florian Fainelli
2018-03-29  5:31         ` Mike Looijmans
2018-03-27  9:52     ` [PATCH v3 2/2] net: macb: Try to retrieve MAC addess from nvmem provider Mike Looijmans
2018-03-28  8:00       ` Nicolas Ferre
2018-03-27 22:43     ` [PATCH v3 0/2] of_net: Implement of_get_nvmem_mac_address helper Andrew Lunn
2018-03-29  5:29     ` [PATCH v4 " Mike Looijmans
2018-03-29  5:29       ` [PATCH v4 1/2] " Mike Looijmans
2018-03-29  5:29       ` [PATCH v4 2/2] net: macb: Try to retrieve MAC addess from nvmem provider Mike Looijmans
2018-03-30 14:40       ` [PATCH v4 0/2] of_net: Implement of_get_nvmem_mac_address helper David Miller
2018-03-31 17:20         ` Mike Looijmans
2018-03-31 17:27           ` Andrew Lunn [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=20180331172735.GC7460@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=frowand.list@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike.looijmans@topic.nl \
    --cc=netdev@vger.kernel.org \
    --cc=robh+dt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox