From: Tom Rini <trini@konsulko.com>
To: Heiko Schocher <hs@denx.de>
Cc: Kyungmin Park <kmpark@infradead.org>,
u-boot@lists.denx.de, John Watts <contact@jookia.org>,
Michael Nazzareno Trimarchi <michael@amarulasolutions.com>
Subject: Re: [PATCH] ubi: Depend on MTD
Date: Fri, 26 Apr 2024 09:52:00 -0600 [thread overview]
Message-ID: <20240426155200.GL1054907@bill-the-cat> (raw)
In-Reply-To: <74dc9d77-9316-4c14-5d52-9b496cad2a76@denx.de>
[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]
On Fri, Apr 26, 2024 at 07:18:18AM +0200, Heiko Schocher wrote:
> Hello Tom,
>
> On 11.04.24 08:09, Michael Nazzareno Trimarchi wrote:
> > Hi
> >
> > On Thu, Apr 11, 2024 at 7:06 AM John Watts <contact@jookia.org> wrote:
> > >
> > > UBI required MTD to build correctly, add it as a Kconfig dependency.
> > >
> > > Signed-off-by: John Watts <contact@jookia.org>
> > > ---
> > > While working with UBI on my SPI NAND patch series I found it was
> > > possible to enable it without enabling the MTD subsystem.
> > > Add a Kconfig option to solve this.
> > > ---
> > > drivers/mtd/ubi/Kconfig | 1 +
> > > 1 file changed, 1 insertion(+)
>
> Seems I am too dummy to find this patch in Patchwork, nor is it
> applied in master ... can you pick it up, or should I do this and
> send you a pull request?
It's over at
https://patchwork.ozlabs.org/project/uboot/patch/20240411-mtd-v1-1-fe300f6ab657@jookia.org/
currently but you can take it up and send it to me if you like.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2024-04-26 15:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 5:05 [PATCH] ubi: Depend on MTD John Watts
2024-04-11 6:09 ` Michael Nazzareno Trimarchi
2024-04-26 5:18 ` Heiko Schocher
2024-04-26 15:52 ` Tom Rini [this message]
2024-04-26 15:56 ` Michael Nazzareno Trimarchi
2024-04-30 6:37 ` Dario Binacchi
2024-04-15 5:55 ` Heiko Schocher
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=20240426155200.GL1054907@bill-the-cat \
--to=trini@konsulko.com \
--cc=contact@jookia.org \
--cc=hs@denx.de \
--cc=kmpark@infradead.org \
--cc=michael@amarulasolutions.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.