From: Patrick DELAUNAY <patrick.delaunay@st.com>
To: u-boot@lists.denx.de
Subject: [PATCH] dfu: Fix handling of UBI partitions in MTD backend
Date: Fri, 23 Oct 2020 15:48:24 +0000 [thread overview]
Message-ID: <5430bc1b353d49f19cb6add25eee2c55@SFHDAG2NODE3.st.com> (raw)
In-Reply-To: <3d869e7f0f024a568f34459f95569b68@SFHDAG6NODE3.st.com>
Hi Lukasz,
> From: U-Boot <u-boot-bounces@lists.denx.de> On Behalf Of Patrick DELAUNAY
> Sent: vendredi 4 septembre 2020 10:31
>
> Hi,
>
> > From: U-Boot <u-boot-bounces@lists.denx.de> On Behalf Of Guillermo
> > Rodriguez
> > Sent: mercredi 2 septembre 2020 13:06
> > To: u-boot at lists.denx.de
> > Cc: Guillermo Rodriguez <guille.rodriguez@gmail.com>; Lukasz Majewski
> > <lukma@denx.de>
> > Subject: [PATCH] dfu: Fix handling of UBI partitions in MTD backend
> >
> > For UBI partitions ("partubi" in dfu_alt_info), dfu_fill_entity_mtd
> > sets the mtd.ubi flag; however other functions incorrectly check for
> > nand.ubi instead. Fix this by checking for the correct flag.
> >
> > Signed-off-by: Guillermo Rodriguez <guille.rodriguez@gmail.com>
> > Cc: Lukasz Majewski <lukma@denx.de>
> > ---
>
> Fixes: 6015af28ee6d ("dfu: add backend for MTD device")
> Reviewed-by: Patrick Delaunay <patrick.delaunay@st.com>
>
> Thanks for the correction.
>
> Patrick
>
> > drivers/dfu/dfu_mtd.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
This correction will be integrated in the next u-boot-dfu v2021.01 pull request ?
Or I can include it in stm32 custodians master branch ?
Patrick
next prev parent reply other threads:[~2020-10-23 15:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 11:06 [PATCH] dfu: Fix handling of UBI partitions in MTD backend Guillermo Rodriguez
2020-09-04 8:31 ` Patrick DELAUNAY
2020-10-23 15:48 ` Patrick DELAUNAY [this message]
2020-10-26 15:33 ` Lukasz Majewski
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=5430bc1b353d49f19cb6add25eee2c55@SFHDAG2NODE3.st.com \
--to=patrick.delaunay@st.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 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.