From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Joel Stanley <joel@jms•id.au>
Cc: Eddie James <eajames@linux•ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build warning after merge of the aspeed tree
Date: Wed, 9 Aug 2023 18:23:22 +1000 [thread overview]
Message-ID: <20230809182322.4b829476@canb.auug.org.au> (raw)
In-Reply-To: <CACPK8XfsVMQEXz3fCFnbii1EbJ_Ev99qjKjXbuLR6nY1BHh4mA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 473 bytes --]
Hi Joel,
On Wed, 9 Aug 2023 07:57:58 +0000 Joel Stanley <joel@jms•id.au> wrote:
>
> On Wed, 2 Aug 2023 at 00:06, Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> > > > Presumably introduced by commit
> > > >
> > > > 267c95dc9f80 ("ARM: dts: aspeed: bonnell: Add DIMM SPD")
> > >
> > > I am still getting those warnings.
> >
> > Any progress with this?
>
> I've pushed some changes that should resolve this.
Thanks
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-08-09 8:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 23:51 linux-next: build warning after merge of the aspeed tree Stephen Rothwell
2023-07-20 0:40 ` Stephen Rothwell
2023-08-02 0:06 ` Stephen Rothwell
2023-08-09 7:57 ` Joel Stanley
2023-08-09 8:23 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-06 23:10 Stephen Rothwell
2020-05-06 23:13 ` Joel Stanley
2020-05-08 6:40 ` Joel Stanley
2020-05-11 15:19 ` Rob Herring
2020-05-20 7:56 ` Joel Stanley
2020-05-22 0:16 ` Stephen Rothwell
2020-05-22 8:15 ` Arnd Bergmann
2020-05-28 6:09 ` Joel Stanley
2020-05-28 7:21 ` Joel Stanley
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=20230809182322.4b829476@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=eajames@linux$(echo .)ibm.com \
--cc=joel@jms$(echo .)id.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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