From: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
To: Simon Glass <sjg@chromium.org>
Cc: Tom Rini <trini@konsulko.com>,
Stefan Herbrechtsmeier <stefan.herbrechtsmeier@weidmueller.com>,
Heiko Schocher <hs@denx.de>,
Tobias Waldekranz <tobias@waldekranz.com>,
Kever Yang <kever.yang@rock-chips.com>,
u-boot@lists.denx.de, "Andrew F . Davis" <afd@ti.com>
Subject: Re: [PATCH 1/1] part: eliminate part_get_info_by_name_type()
Date: Wed, 19 Jul 2023 04:17:23 +0200 [thread overview]
Message-ID: <11919cfa-893b-0e85-05ff-3516fa05a447@canonical.com> (raw)
In-Reply-To: <CAPnjgZ0gWbun6VFwrG=fj2SoFB4ukJzA1h_Vs-HzNDzyArRLpA@mail.gmail.com>
On 7/19/23 03:08, Simon Glass wrote:
> Hi Heinrich,
>
> On Sun, 16 Jul 2023 at 05:34, Heinrich Schuchardt
> <heinrich.schuchardt@canonical.com> wrote:
>>
>> Since commit 56670d6fb83f ("disk: part: use common api to lookup part
>> driver") part_get_info_by_name_type() ignores the part_type parameter
>> used to restrict the partition table type.
>>
>> omap_mmc_get_part_size() and part_get_info_by_name() are the only
>> consumers.
>>
>> omap_mmc_get_part_size() calls with part_type = PART_TYPE_EFI because at
>> the time of implementation a speed up could be gained by passing the
>> partition table type. After 5 years experience without this restriction
>> it looks safe to keep it that way.
>>
>> part_get_info_by_name() uses PART_TYPE_ALL.
>>
>> Move the logic of part_get_info_by_name_type() to part_get_info_by_name()
>> and replace the function in omap_mmc_get_part_size().
>>
>> Fixes: 56670d6fb83f ("disk: part: use common api to lookup part driver")
>> Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
>> ---
>> arch/arm/mach-omap2/utils.c | 3 +--
>> disk/part.c | 10 ++--------
>> include/part.h | 23 -----------------------
>> 3 files changed, 3 insertions(+), 33 deletions(-)
>
> That explains the strange behaviour I saw when fiddling with this a
> month or so back, thanks.
>
> Reviewed-by: Simon Glass <sjg@chromium.org>
>
> Is there a test to update for this?
Thanks for reviewing.
As we don't change any existing behavior there is no test to update.
Best regards
Heinrich
next prev parent reply other threads:[~2023-07-19 2:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-16 11:34 [PATCH 1/1] part: eliminate part_get_info_by_name_type() Heinrich Schuchardt
2023-07-19 1:08 ` Simon Glass
2023-07-19 2:17 ` Heinrich Schuchardt [this message]
2023-07-25 21:13 ` Tom Rini
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=11919cfa-893b-0e85-05ff-3516fa05a447@canonical.com \
--to=heinrich.schuchardt@canonical.com \
--cc=afd@ti.com \
--cc=hs@denx.de \
--cc=kever.yang@rock-chips.com \
--cc=sjg@chromium.org \
--cc=stefan.herbrechtsmeier@weidmueller.com \
--cc=tobias@waldekranz.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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