From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Rob Herring <robh@kernel.org>
Cc: John Crispin <john@phrozen.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: Fixup explicit DT include clean-up
Date: Fri, 28 Jul 2023 11:48:26 +0200 [thread overview]
Message-ID: <ZMOO6hsbRAQCOORg@alpha.franken.de> (raw)
In-Reply-To: <20230727012028.3933785-1-robh@kernel.org>
On Wed, Jul 26, 2023 at 07:20:28PM -0600, Rob Herring wrote:
> Commit 657c45b303f87d77 ("MIPS: Explicitly include correct DT includes")
> removed a necessary include by mistake and missed adding an explicit
> include of spinlock.h (from of.h -> kobject.h -> spinlock.h).
>
> Fixes: 657c45b303f87d77 ("MIPS: Explicitly include correct DT includes")
> Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> arch/mips/lantiq/xway/gptu.c | 1 +
> arch/mips/pic32/pic32mzda/config.c | 1 +
> 2 files changed, 2 insertions(+)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2023-07-28 9:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 1:20 [PATCH] MIPS: Fixup explicit DT include clean-up Rob Herring
2023-07-28 9:48 ` Thomas Bogendoerfer [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=ZMOO6hsbRAQCOORg@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=geert@linux-m68k.org \
--cc=john@phrozen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=robh@kernel.org \
/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