From: Johan Hovold <johan@kernel.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: Daniel Thompson <daniel.thompson@linaro.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Jingoo Han <jingoohan1@gmail.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Johan Hovold <johan@kernel.org>,
linux-fbdev@vger.kernel.org
Subject: Re: [PATCH v2 0/4] backlight: fix device-tree node lookups
Date: Fri, 11 May 2018 07:27:31 +0000 [thread overview]
Message-ID: <20180511072731.GA17870@localhost> (raw)
In-Reply-To: <20171120104547.2639-1-johan@kernel.org>
Hi Lee,
On Mon, Nov 20, 2017 at 11:45:43AM +0100, Johan Hovold wrote:
> A number of drivers have been using the wrong OF helper when doing child-node
> lookups during probe. This meant that they were doing tree-wide searches rather
> than matching on child nodes and that the parent node could end up being
> prematurely freed.
> Johan Hovold (4):
> backlight: as3711_bl: fix device-tree node lookup
> backlight: max8925_bl: fix device-tree node lookup
> backlight: tps65217_bl: fix device-tree node lookup
> backlight: as3711_bl: fix device-tree node leaks
It appears these four have been sitting in your for-backlight-fixes
branch for half a year now without being forwarded to Linus.
Don't get many backlight fixes these days, huh? ;)
Thanks,
Johan
WARNING: multiple messages have this Message-ID (diff)
From: Johan Hovold <johan@kernel.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: Daniel Thompson <daniel.thompson@linaro.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Jingoo Han <jingoohan1@gmail.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Johan Hovold <johan@kernel.org>,
linux-fbdev@vger.kernel.org
Subject: Re: [PATCH v2 0/4] backlight: fix device-tree node lookups
Date: Fri, 11 May 2018 09:27:31 +0200 [thread overview]
Message-ID: <20180511072731.GA17870@localhost> (raw)
In-Reply-To: <20171120104547.2639-1-johan@kernel.org>
Hi Lee,
On Mon, Nov 20, 2017 at 11:45:43AM +0100, Johan Hovold wrote:
> A number of drivers have been using the wrong OF helper when doing child-node
> lookups during probe. This meant that they were doing tree-wide searches rather
> than matching on child nodes and that the parent node could end up being
> prematurely freed.
> Johan Hovold (4):
> backlight: as3711_bl: fix device-tree node lookup
> backlight: max8925_bl: fix device-tree node lookup
> backlight: tps65217_bl: fix device-tree node lookup
> backlight: as3711_bl: fix device-tree node leaks
It appears these four have been sitting in your for-backlight-fixes
branch for half a year now without being forwarded to Linus.
Don't get many backlight fixes these days, huh? ;)
Thanks,
Johan
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Johan Hovold <johan@kernel.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: Daniel Thompson <daniel.thompson@linaro.org>,
Jingoo Han <jingoohan1@gmail.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org, Johan Hovold <johan@kernel.org>
Subject: Re: [PATCH v2 0/4] backlight: fix device-tree node lookups
Date: Fri, 11 May 2018 09:27:31 +0200 [thread overview]
Message-ID: <20180511072731.GA17870@localhost> (raw)
In-Reply-To: <20171120104547.2639-1-johan@kernel.org>
Hi Lee,
On Mon, Nov 20, 2017 at 11:45:43AM +0100, Johan Hovold wrote:
> A number of drivers have been using the wrong OF helper when doing child-node
> lookups during probe. This meant that they were doing tree-wide searches rather
> than matching on child nodes and that the parent node could end up being
> prematurely freed.
> Johan Hovold (4):
> backlight: as3711_bl: fix device-tree node lookup
> backlight: max8925_bl: fix device-tree node lookup
> backlight: tps65217_bl: fix device-tree node lookup
> backlight: as3711_bl: fix device-tree node leaks
It appears these four have been sitting in your for-backlight-fixes
branch for half a year now without being forwarded to Linus.
Don't get many backlight fixes these days, huh? ;)
Thanks,
Johan
next prev parent reply other threads:[~2018-05-11 7:27 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 10:45 [PATCH v2 0/4] backlight: fix device-tree node lookups Johan Hovold
2017-11-20 10:45 ` Johan Hovold
2017-11-20 10:45 ` [PATCH v2 1/4] backlight: as3711_bl: fix device-tree node lookup Johan Hovold
2017-11-20 10:45 ` Johan Hovold
2017-11-20 11:33 ` Daniel Thompson
2017-11-20 11:33 ` Daniel Thompson
2017-11-29 11:28 ` Lee Jones
2017-11-29 11:28 ` Lee Jones
2017-11-29 11:28 ` Lee Jones
2017-11-20 10:45 ` [PATCH v2 2/4] backlight: max8925_bl: " Johan Hovold
2017-11-20 10:45 ` Johan Hovold
2017-11-20 11:33 ` Daniel Thompson
2017-11-20 11:33 ` Daniel Thompson
2017-11-20 11:33 ` Daniel Thompson
2017-11-29 11:29 ` Lee Jones
2017-11-29 11:29 ` Lee Jones
2017-11-20 10:45 ` [PATCH v2 3/4] backlight: tps65217_bl: " Johan Hovold
2017-11-20 10:45 ` Johan Hovold
2017-11-20 11:34 ` Daniel Thompson
2017-11-20 11:34 ` Daniel Thompson
2017-11-20 11:34 ` Daniel Thompson
2017-11-20 11:44 ` Johan Hovold
2017-11-20 11:44 ` Johan Hovold
2017-11-29 11:29 ` Lee Jones
2017-11-29 11:29 ` Lee Jones
2017-11-20 10:45 ` [PATCH v2 4/4] backlight: as3711_bl: fix device-tree node leaks Johan Hovold
2017-11-20 10:45 ` Johan Hovold
2017-11-20 11:41 ` Daniel Thompson
2017-11-20 11:41 ` Daniel Thompson
2017-11-20 11:41 ` Daniel Thompson
2017-11-29 11:29 ` Lee Jones
2017-11-29 11:29 ` Lee Jones
2017-11-29 11:29 ` Lee Jones
2018-05-11 7:27 ` Johan Hovold [this message]
2018-05-11 7:27 ` [PATCH v2 0/4] backlight: fix device-tree node lookups Johan Hovold
2018-05-11 7:27 ` Johan Hovold
2018-05-11 8:13 ` Lee Jones
2018-05-11 8:13 ` Lee Jones
2018-05-11 8:13 ` Lee Jones
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=20180511072731.GA17870@localhost \
--to=johan@kernel.org \
--cc=b.zolnierkie@samsung.com \
--cc=daniel.thompson@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jingoohan1@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 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.