public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	David Woodhouse <David.Woodhouse@intel.com>,
	Akinobu Mita <akinobu.mita@gmail.com>,
	Artem Bityutskiy <artem.bityutskiy@linux.intel.com>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: make mtd_test.c a separate module
Date: Wed, 29 May 2024 14:13:23 +0200	[thread overview]
Message-ID: <20240529141323.7015f3d9@xps-13> (raw)
In-Reply-To: <20240529095049.1915393-1-arnd@kernel.org>

Hi Arnd,

arnd@kernel.org wrote on Wed, 29 May 2024 11:50:39 +0200:

> From: Arnd Bergmann <arnd@arndb.de>
> 
> This file gets linked into nine different modules, which causes a warning:
> 
> scripts/Makefile.build:236: drivers/mtd/tests/Makefile: mtd_test.o is added to multiple modules: mtd_nandbiterrs mtd_oobtest mtd_pagetest mtd_readtest mtd_speedtest mtd_stresstest mtd_subpagetest mtd_torturetest

I've never experienced this warning myself, how did you produce it?

> Make it a separate module instead.

I'm not a total fan of this just because it now requires an additional
step to insert these test modules (they are likely used for
debugging/development purposes, so not properly installed in the
rootfs). Is there any chance we can find another way?

Thanks,
Miquèl

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2024-05-29 12:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-29  9:50 [PATCH] mtd: make mtd_test.c a separate module Arnd Bergmann
2024-05-29 12:13 ` Miquel Raynal [this message]
2024-05-29 12:36   ` Arnd Bergmann
2024-05-30 13:45     ` Miquel Raynal
2024-07-01 12:00 ` Miquel Raynal

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=20240529141323.7015f3d9@xps-13 \
    --to=miquel.raynal@bootlin.com \
    --cc=David.Woodhouse@intel.com \
    --cc=akinobu.mita@gmail.com \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=artem.bityutskiy@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --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