From: Richard Weinberger <richard.weinberger@gmail.com>
To: Tudor Ambarus <Tudor.Ambarus@microchip.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
Boris Brezillon <bbrezillon@kernel.org>,
Richard Weinberger <richard@nod.at>,
LKML <linux-kernel@vger.kernel.org>,
linux-mtd@lists.infradead.org,
Miquel Raynal <miquel.raynal@bootlin.com>,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH] mtd: spi-nor: Compile files in controllers/ directory
Date: Thu, 9 Apr 2020 22:01:27 +0200 [thread overview]
Message-ID: <CAFLxGvwKuYYA8S+J=CgXniPa2cQJ_vp-0Q_APkxKNPJX_TuWaw@mail.gmail.com> (raw)
In-Reply-To: <1671412.OU26QM6KFd@192.168.0.120>
On Mon, Apr 6, 2020 at 7:31 AM <Tudor.Ambarus@microchip.com> wrote:
>
> On Saturday, April 4, 2020 6:36:31 PM EEST Guenter Roeck wrote:
> > Commit a0900d0195d2 ("mtd: spi-nor: Prepare core / manufacturer code
> > split") moved various files into a new directory, but did not add the new
> > directory to its parent directory Makefile. The moved files no longer
> > build, and affected flash chips no longer instantiate.
> >
> > Adding the new directory to the parent directory Makefile fixes the
> > problem.
> >
> > Fixes: a0900d0195d2 ("mtd: spi-nor: Prepare core / manufacturer code split")
> > Cc: Boris Brezillon <bbrezillon@kernel.org>
> > Cc: Tudor Ambarus <tudor.ambarus@microchip.com>
> > Signed-off-by: Guenter Roeck <linux@roeck-us.net>
> > ---
> > drivers/mtd/spi-nor/Makefile | 2 ++
> > 1 file changed, 2 insertions(+)
>
> Reviewed-by: Tudor Ambarus <tudor.ambarus@microchip.com>
>
> I missed that somehow, sorry. Thank you for the fix, Guenter!
Applied to mtd/fixes, thanks to everyone for addressing this.
--
Thanks,
//richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2020-04-09 20:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-04 15:36 [PATCH] mtd: spi-nor: Compile files in controllers/ directory Guenter Roeck
2020-04-04 15:40 ` Boris Brezillon
2020-04-06 1:20 ` Joel Stanley
2020-04-06 5:31 ` Tudor.Ambarus
2020-04-09 20:01 ` Richard Weinberger [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='CAFLxGvwKuYYA8S+J=CgXniPa2cQJ_vp-0Q_APkxKNPJX_TuWaw@mail.gmail.com' \
--to=richard.weinberger@gmail.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=bbrezillon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux@roeck-us.net \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.com \
/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;
as well as URLs for NNTP newsgroup(s).