All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Doug Berger <opendmb@gmail.com>,
	bcm-kernel-feedback-list@broadcom.com,
	"David S. Miller" <davem@davemloft.net>,
	netdev@vger.kernel.org
Subject: Re: [PATCH v1 1/2] net: bcmgenet: Drop ACPI_PTR() to avoid compiler warning
Date: Tue, 21 Apr 2020 00:26:06 +0300	[thread overview]
Message-ID: <20200420212606.GD185537@smile.fi.intel.com> (raw)
In-Reply-To: <d193529a-57af-b694-32e4-cd64455c6a96@gmail.com>

On Mon, Apr 20, 2020 at 11:18:34AM -0700, Florian Fainelli wrote:
> 
> 
> On 4/20/2020 11:16 AM, Andy Shevchenko wrote:
> > When compiled with CONFIG_ACPI=n, ACPI_PTR() will be no-op, and thus
> > genet_acpi_match table defined, but not used. Compiler is not happy about
> > such data. Drop ACPI_PTR() for good.
> > 
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> 
> Acked-by: Florian Fainelli <f.fainelli@gmail.com>

Thank you!

Please, do not apply this, I will combine all patches together in a series.
I have more because of that ACPI enabling work.

-- 
With Best Regards,
Andy Shevchenko



      reply	other threads:[~2020-04-20 21:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20 18:16 [PATCH v1 1/2] net: bcmgenet: Drop ACPI_PTR() to avoid compiler warning Andy Shevchenko
2020-04-20 18:16 ` [PATCH v1 2/2] net: bcmgenet: Drop useless OF code Andy Shevchenko
2020-04-20 18:19   ` Florian Fainelli
2020-04-20 18:18 ` [PATCH v1 1/2] net: bcmgenet: Drop ACPI_PTR() to avoid compiler warning Florian Fainelli
2020-04-20 21:26   ` Andy Shevchenko [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=20200420212606.GD185537@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=opendmb@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 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.