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>,
linux-media <linux-media@vger.kernel.org>,
"Jacopo Mondi" <jacopo+renesas@jmondi.org>,
"Kieran Bingham" <kieran.bingham+renesas@ideasonboard.com>,
"Laurent Pinchart" <laurent.pinchart+renesas@ideasonboard.com>,
"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Subject: Re: linux-next: Tree for Aug 13 (drivers/media/i2c/max9286.c)
Date: Thu, 13 Aug 2020 11:35:30 -0700 [thread overview]
Message-ID: <17a1c5aa-2f38-c84d-bf2d-485862dc0615@infradead.org> (raw)
In-Reply-To: <20200813165846.27887669@canb.auug.org.au>
On 8/12/20 11:58 PM, Stephen Rothwell wrote:
> Hi all,
>
> News: The merge window has opened, so please do not add any v5.10
> related material to your linux-next included branches until after the
> merge window closes again.
>
> Changes since 20200812:
>
on x86_64:
# CONFIG_GPIOLIB is not set
../drivers/media/i2c/max9286.c: In function 'max9286_register_gpio':
../drivers/media/i2c/max9286.c:1033:6: error: 'struct gpio_chip' has no member named 'of_node'
gpio->of_node = dev->of_node;
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
next prev parent reply other threads:[~2020-08-13 18:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-13 6:58 linux-next: Tree for Aug 13 Stephen Rothwell
2020-08-13 11:00 ` nvme crash - " John Garry
2020-08-13 15:50 ` Christoph Hellwig
2020-08-14 12:00 ` John Garry
2020-08-14 12:08 ` Christoph Hellwig
2020-08-14 13:07 ` John Garry
2020-08-14 13:37 ` John Garry
2020-08-13 14:41 ` linux-next: Tree for Aug 13 [drivers/staging/vc04_services/bcm2835-camera/] Randy Dunlap
2020-08-13 18:35 ` Randy Dunlap [this message]
2020-08-13 19:01 ` linux-next: Tree for Aug 13 (drivers/media/i2c/max9286.c) Kieran Bingham
2020-08-13 21:55 ` Sakari Ailus
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=17a1c5aa-2f38-c84d-bf2d-485862dc0615@infradead.org \
--to=rdunlap@infradead.org \
--cc=jacopo+renesas@jmondi.org \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
--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).