The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Conor Dooley <conor.dooley@microchip.com>
To: Arnd Bergmann <arnd@kernel.org>
Cc: "Ulf Hansson" <ulf.hansson@linaro.org>,
	"Arnd Bergmann" <arnd@arndb.de>, "Joel Stanley" <joel@jms.id.au>,
	"Walker Chen" <walker.chen@starfivetech.com>,
	"Paul Menzel" <pmenzel@molgen.mpg.de>,
	"Yinbo Zhu" <zhuyinbo@loongson.cn>,
	"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
	"Emil Renner Berthing" <kernel@esmil.dk>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] soc: starfive: remove stale Makefile entry
Date: Wed, 26 Jul 2023 13:33:50 +0100	[thread overview]
Message-ID: <20230726-target-flashy-b9033ea36ae4@wendy> (raw)
In-Reply-To: <20230726121724.3701240-1-arnd@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 682 bytes --]

On Wed, Jul 26, 2023 at 02:17:14PM +0200, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
> 
> After the only starfive driver was moved out to the genpd subsystem, we get
> a build failure:
> 
> scripts/Makefile.build:41: drivers/soc/starfive/Makefile: No such file or directory
> 
> Fixes: f3fb16291f486 ("soc: starfive: Move the power-domain driver to the genpd dir")

> Reported=by: kernel test robot <lkp@intel.com

There's a - & a missing > in this tag.
Otherwise,
Acked-by: Conor Dooley <conor.dooley@microchip.com>

Reminds me, I need to also send a patch moving the Kconfig entry &
delete the directory and MAINTAINERS entry.

Thanks,
Conor.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      parent reply	other threads:[~2023-07-26 12:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-26 12:17 [PATCH 1/2] soc: starfive: remove stale Makefile entry Arnd Bergmann
2023-07-26 12:17 ` [PATCH 2/2] genpd: move owl-sps-helper.c from drivers/soc Arnd Bergmann
2023-07-26 12:26   ` Ulf Hansson
2023-07-26 12:26 ` [PATCH 1/2] soc: starfive: remove stale Makefile entry Ulf Hansson
2023-07-26 12:33 ` Conor Dooley [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=20230726-target-flashy-b9033ea36ae4@wendy \
    --to=conor.dooley@microchip.com \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=j.neuschaefer@gmx.net \
    --cc=joel@jms.id.au \
    --cc=kernel@esmil.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmenzel@molgen.mpg.de \
    --cc=ulf.hansson@linaro.org \
    --cc=walker.chen@starfivetech.com \
    --cc=zhuyinbo@loongson.cn \
    /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