linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Joel Stanley <joel@jms.id.au>
Cc: Andrew Jeffery <andrew@aj.id.au>, arm <arm@kernel.org>,
	linux-aspeed@lists.ozlabs.org,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] ARM: aspeed: defconfig changes for 5.3
Date: Wed, 26 Jun 2019 19:18:08 -0700	[thread overview]
Message-ID: <20190627021808.47q4n4bhrj75hxzw@localhost> (raw)
In-Reply-To: <CACPK8Xf=vb4To_fxpJiaT-is3BBGg1SUsAc1qtFrBd-FwmPXRA@mail.gmail.com>

On Wed, Jun 26, 2019 at 02:03:45AM +0000, Joel Stanley wrote:
> On Tue, 25 Jun 2019 at 13:18, Olof Johansson <olof@lixom.net> wrote:
> >
> > Hi,
> >
> > Looks like the multi_v5_defconfig changes aren't producing the results
> > you're probably expecting -- unless the drivers are pending in
> > linux-next?
> >
> > arch/arm/configs/multi_v5_defconfig:257:warning: override: reassigning
> > to symbol ASPEED_LPC_CTRL
> > arch/arm/configs/multi_v5_defconfig:258:warning: override: reassigning
> > to symbol ASPEED_LPC_SNOOP
> 
> Oops, sorry. I made a mistake when preparing the change and missed the
> warning when testing. We now have two copies of each of these options
> in the defconfig (they moved around due to misc -> soc movement).

No worries!

> I've sent a follow up patch for you to apply directly. Let me know if
> that's okay, otherwise I can do a new tag.

Patch was fine, applied.


-Olof

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2019-06-27  5:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-22  7:58 [GIT PULL] ARM: aspeed: defconfig changes for 5.3 Joel Stanley
2019-06-25 12:21 ` Olof Johansson
2019-06-25 13:18 ` Olof Johansson
2019-06-26  2:03   ` Joel Stanley
2019-06-27  2:18     ` Olof Johansson [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=20190627021808.47q4n4bhrj75hxzw@localhost \
    --to=olof@lixom.net \
    --cc=andrew@aj.id.au \
    --cc=arm@kernel.org \
    --cc=joel@jms.id.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).