From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
LAK <linux-arm-kernel@lists.infradead.org>,
Microchip Linux Driver Support <UNGLinuxDriver@microchip.com>,
Steen Hegelund <Steen.Hegelund@microchip.com>,
Lars Povlsen <lars.povlsen@microchip.com>,
Linus Walleij <linus.walleij@linaro.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: linux-next: Tree for Nov 24 (drivers/pinctrl/pinctrl-microchip-sgpio.c)
Date: Tue, 24 Nov 2020 10:37:03 -0800 [thread overview]
Message-ID: <75ff21c9-57af-0dcd-6eb5-d87e3abeaf70@infradead.org> (raw)
In-Reply-To: <20201124180712.1fd45b2e@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 788 bytes --]
On 11/23/20 11:07 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20201123:
>
on i386 or x86_64:
# CONFIG_OF is not set
../drivers/pinctrl/pinctrl-microchip-sgpio.c: In function ‘microchip_sgpio_register_bank’:
../drivers/pinctrl/pinctrl-microchip-sgpio.c:597:4: error: ‘struct gpio_chip’ has no member named ‘of_node’
gc->of_node = to_of_node(fwnode);
^~
../drivers/pinctrl/pinctrl-microchip-sgpio.c:606:4: error: ‘struct gpio_chip’ has no member named ‘of_xlate’
gc->of_xlate = microchip_sgpio_of_xlate;
^~
../drivers/pinctrl/pinctrl-microchip-sgpio.c:607:4: error: ‘struct gpio_chip’ has no member named ‘of_gpio_n_cells’
gc->of_gpio_n_cells = 3;
^~
Full randconfig file is attached.
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
[-- Attachment #2: config-r6380.xz --]
[-- Type: application/x-xz, Size: 24940 bytes --]
prev parent reply other threads:[~2020-11-24 18:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 7:07 linux-next: Tree for Nov 24 Stephen Rothwell
2020-11-24 18:37 ` Randy Dunlap [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=75ff21c9-57af-0dcd-6eb5-d87e3abeaf70@infradead.org \
--to=rdunlap@infradead.org \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=lars.povlsen@microchip.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).