From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
Cc: "Randy Dunlap" <rdunlap@infradead.org>,
"Stephen Rothwell" <sfr@canb.auug.org.au>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
linux-media <linux-media@vger.kernel.org>,
"Jacopo Mondi" <jacopo+renesas@jmondi.org>,
"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: Fri, 14 Aug 2020 00:55:05 +0300 [thread overview]
Message-ID: <20200813215505.GC24582@paasikivi.fi.intel.com> (raw)
In-Reply-To: <3262a9fc-46e2-3109-3764-e7153edf486d@ideasonboard.com>
Hi Kieran,
On Thu, Aug 13, 2020 at 08:01:01PM +0100, Kieran Bingham wrote:
> Hi Randy,
>
> On 13/08/2020 19:35, Randy Dunlap wrote:
> > 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;
> >
>
> Thanks for the report, Sakari has already submitted a fix [0] for this.
> I assume it just needs a nudge to get picked up via Mauro's tree.
>
> [0]
> https://lore.kernel.org/linux-media/20200803090935.23619-1-sakari.ailus@linux.intel.com/
Yes. I'll send a pull request soon.
--
Sakari Ailus
prev parent reply other threads:[~2020-08-13 21:55 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 ` linux-next: Tree for Aug 13 (drivers/media/i2c/max9286.c) Randy Dunlap
2020-08-13 19:01 ` Kieran Bingham
2020-08-13 21:55 ` Sakari Ailus [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=20200813215505.GC24582@paasikivi.fi.intel.com \
--to=sakari.ailus@linux.intel.com \
--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=mchehab@kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=rdunlap@infradead.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).