From: David Miller <davem@davemloft.net>
To: rdunlap@infradead.org
Cc: netdev@vger.kernel.org, madalin.bucur@nxp.com,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] net/ethernet/freescale/fman: fix cross-build error
Date: Mon, 16 Jul 2018 14:03:00 -0700 (PDT) [thread overview]
Message-ID: <20180716.140300.318968566584687896.davem@davemloft.net> (raw)
In-Reply-To: <3a063d78-73f8-b41f-9354-fe839fe80c11@infradead.org>
From: Randy Dunlap <rdunlap@infradead.org>
Date: Fri, 13 Jul 2018 21:25:19 -0700
> From: Randy Dunlap <rdunlap@infradead.org>
>
> CC [M] drivers/net/ethernet/freescale/fman/fman.o
> In file included from ../drivers/net/ethernet/freescale/fman/fman.c:35:
> ../include/linux/fsl/guts.h: In function 'guts_set_dmacr':
> ../include/linux/fsl/guts.h:165:2: error: implicit declaration of function 'clrsetbits_be32' [-Werror=implicit-function-declaration]
> clrsetbits_be32(&guts->dmacr, 3 << shift, device << shift);
> ^~~~~~~~~~~~~~~
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Applied.
prev parent reply other threads:[~2018-07-16 21:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-14 4:25 [PATCH] net/ethernet/freescale/fman: fix cross-build error Randy Dunlap
2018-07-16 21:03 ` David Miller [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=20180716.140300.318968566584687896.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madalin.bucur@nxp.com \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).