From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>,
Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH 0/7] replace cdev_by_name() with cdev_open_by_name()
Date: Tue, 21 May 2024 08:17:58 +0200 [thread overview]
Message-ID: <171627227800.1428178.6212792306461694761.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20240516070822.2746845-1-s.hauer@pengutronix.de>
On Thu, 16 May 2024 09:08:15 +0200, Sascha Hauer wrote:
> As Ahmad noticed cdev_by_name() doesn't increase the reference counting
> on the returned cdev which causes problems further down the road. This
> series replaces some of the easier occurences of cdev_by_name() with
> cdev_open_by_name().
>
> Sascha Hauer (7):
> ARM: Freescale i.MX23 evk: use cdev_open_by_name()
> ARM: tx28: use cdev_open_by_name()
> ARM: omap: use cdev_open_by_name()
> ARM: Rockchip: use cdev_open_by_name()
> commands: devlookup: use cdev_open_by_name()
> commands: findmnt: use cdev_open_by_name()
> bootm: use cdev_open_by_name()
>
> [...]
Applied, thanks!
[1/7] ARM: Freescale i.MX23 evk: use cdev_open_by_name()
https://git.pengutronix.de/cgit/barebox/commit/?id=3111bf9b13d2 (link may not be stable)
[2/7] ARM: tx28: use cdev_open_by_name()
https://git.pengutronix.de/cgit/barebox/commit/?id=05164ce75799 (link may not be stable)
[3/7] ARM: omap: use cdev_open_by_name()
https://git.pengutronix.de/cgit/barebox/commit/?id=50788af27a89 (link may not be stable)
[4/7] ARM: Rockchip: use cdev_open_by_name()
https://git.pengutronix.de/cgit/barebox/commit/?id=9da41e4d65fc (link may not be stable)
[5/7] commands: devlookup: use cdev_open_by_name()
https://git.pengutronix.de/cgit/barebox/commit/?id=bc5868b647aa (link may not be stable)
[6/7] commands: findmnt: use cdev_open_by_name()
https://git.pengutronix.de/cgit/barebox/commit/?id=7aa92b02b84a (link may not be stable)
[7/7] bootm: use cdev_open_by_name()
https://git.pengutronix.de/cgit/barebox/commit/?id=888a17fa7e95 (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2024-05-21 6:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 7:08 Sascha Hauer
2024-05-16 7:08 ` [PATCH 1/7] ARM: Freescale i.MX23 evk: use cdev_open_by_name() Sascha Hauer
2024-05-16 7:08 ` [PATCH 2/7] ARM: tx28: " Sascha Hauer
2024-05-16 7:08 ` [PATCH 3/7] ARM: omap: " Sascha Hauer
2024-05-16 7:08 ` [PATCH 4/7] ARM: Rockchip: " Sascha Hauer
2024-05-16 7:08 ` [PATCH 5/7] commands: devlookup: " Sascha Hauer
2024-05-16 7:08 ` [PATCH 6/7] commands: findmnt: " Sascha Hauer
2024-05-16 7:08 ` [PATCH 7/7] bootm: " Sascha Hauer
2024-05-16 14:43 ` [PATCH 0/7] replace cdev_by_name() with cdev_open_by_name() Marco Felsch
2024-05-16 15:01 ` Sascha Hauer
2024-05-21 6:17 ` Sascha Hauer [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=171627227800.1428178.6212792306461694761.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.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