mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH 1/8] treewide: replace dev_get_drvdata with device_get_match_data
Date: Tue, 06 May 2025 09:41:12 +0200	[thread overview]
Message-ID: <174651727233.3193283.9837045386397797332.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20250506063446.3133582-1-a.fatoum@pengutronix.de>


On Tue, 06 May 2025 08:34:39 +0200, Ahmad Fatoum wrote:
> Both Linux and barebox define a dev_get_drvdata function, but
> annoyingly, the barebox version accesses the private data set in the
> probe function, while the Linux version retrieves the match data set by
> the driver core instead.
> 
> In preparation for changing the function to have the Linux semantics,
> start by replacing most instances in barebox with device_get_match_data.
> 
> [...]

Applied, thanks!

[1/8] treewide: replace dev_get_drvdata with device_get_match_data
      https://git.pengutronix.de/cgit/barebox/commit/?id=20d87123a638 (link may not be stable)
[2/8] ARM: i.MX: esdctl: replace dev_get_drvdata with device_get_match_data
      https://git.pengutronix.de/cgit/barebox/commit/?id=443b268313cd (link may not be stable)
[3/8] driver: switch dev_get_drvdata to Linux semantics
      https://git.pengutronix.de/cgit/barebox/commit/?id=d2ffe93877b9 (link may not be stable)
[4/8] gpio: gpio-mxs: replace dev_get_drvdata with device_get_match_data
      https://git.pengutronix.de/cgit/barebox/commit/?id=0bac10a83bb9 (link may not be stable)
[5/8] mci: am654-sdhci: fix error code printed in error messages
      https://git.pengutronix.de/cgit/barebox/commit/?id=aeefd448d91c (link may not be stable)
[6/8] pinctrl: at91: replace dev_get_drvdata with device_get_match_data
      https://git.pengutronix.de/cgit/barebox/commit/?id=3142ec714275 (link may not be stable)
[7/8] drivers: maintain const when converting from struct driver
      https://git.pengutronix.de/cgit/barebox/commit/?id=61c1bc52072d (link may not be stable)
[8/8] driver: base: invert driver match callback for Linux compatibility
      https://git.pengutronix.de/cgit/barebox/commit/?id=64ca71016300 (link may not be stable)

Best regards,
-- 
Sascha Hauer <s.hauer@pengutronix.de>




      parent reply	other threads:[~2025-05-06  7:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-06  6:34 Ahmad Fatoum
2025-05-06  6:34 ` [PATCH 2/8] ARM: i.MX: esdctl: " Ahmad Fatoum
2025-05-06  6:34 ` [PATCH 3/8] driver: switch dev_get_drvdata to Linux semantics Ahmad Fatoum
2025-05-06  6:34 ` [PATCH 4/8] gpio: gpio-mxs: replace dev_get_drvdata with device_get_match_data Ahmad Fatoum
2025-05-06  7:42   ` Sascha Hauer
2025-05-06  6:34 ` [PATCH 5/8] mci: am654-sdhci: fix error code printed in error messages Ahmad Fatoum
2025-05-06  6:34 ` [PATCH 6/8] pinctrl: at91: replace dev_get_drvdata with device_get_match_data Ahmad Fatoum
2025-05-06  6:34 ` [PATCH 7/8] drivers: maintain const when converting from struct driver Ahmad Fatoum
2025-05-06  6:34 ` [PATCH 8/8] driver: base: invert driver match callback for Linux compatibility Ahmad Fatoum
2025-05-06  7:41 ` 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=174651727233.3193283.9837045386397797332.b4-ty@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=a.fatoum@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