mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@kernel.org>
To: Herve Codina <herve.codina@bootlin.com>,
	Qiang Zhao <qiang.zhao@nxp.com>, Li Yang <leoyang.li@nxp.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linuxppc-dev@lists.ozlabs.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
	Mark Brown <broonie@kernel.org>,
	Christophe Leroy <christophe.leroy@csgroup.eu>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH 0/2] Fix COMPILE_TEST dependencies for CPM uart, TSA and QMC
Date: Tue, 23 May 2023 09:48:28 +0200	[thread overview]
Message-ID: <e8c45035-1834-7214-46af-834e879cf3c5@kernel.org> (raw)
In-Reply-To: <20230522082048.21216-1-herve.codina@bootlin.com>

On 22. 05. 23, 10:20, Herve Codina wrote:
> This series fixes issues raised by the kernel test robot
>    https://lore.kernel.org/oe-kbuild-all/202305160221.9XgweObz-lkp@intel.com/
> 
> In COMPILE_TEST configurations, TSA and QMC need CONFIG_CPM to be set in
> order to compile and CPM uart needs CONFIG_CPM2.

Ah, perfect. Greg, please disregard my revert posted at:
   https://lore.kernel.org/all/20230518055620.29957-1-jirislaby@kernel.org/

and take these instead.

Thanks.

> Best regards,
> Hervé
> 
> Herve Codina (2):
>    soc: fsl: cpm1: Fix TSA and QMC dependencies in case of COMPILE_TEST
>    serial: cpm_uart: Fix a COMPILE_TEST dependency
> 
>   drivers/soc/fsl/qe/Kconfig | 4 ++--
>   drivers/tty/serial/Kconfig | 2 +-
>   2 files changed, 3 insertions(+), 3 deletions(-)
> 

-- 
js


      parent reply	other threads:[~2023-05-23  7:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-22  8:20 Herve Codina
2023-05-22  8:20 ` [PATCH 1/2] soc: fsl: cpm1: Fix TSA and QMC dependencies in case of COMPILE_TEST Herve Codina
2023-05-22  8:20 ` [PATCH 2/2] serial: cpm_uart: Fix a COMPILE_TEST dependency Herve Codina
2023-05-23  7:52   ` Jiri Slaby
2023-05-23  8:36     ` Herve Codina
2023-05-23  7:48 ` Jiri Slaby [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=e8c45035-1834-7214-46af-834e879cf3c5@kernel.org \
    --to=jirislaby@kernel.org \
    --cc=broonie@kernel.org \
    --cc=christophe.leroy@csgroup.eu \
    --cc=gregkh@linuxfoundation.org \
    --cc=herve.codina@bootlin.com \
    --cc=leoyang.li@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=qiang.zhao@nxp.com \
    --cc=thomas.petazzoni@bootlin.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
all inboxes | Powered by JetHome®