linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Build regressions/improvements in v4.0-rc3
Date: Mon, 9 Mar 2015 15:27:22 +0100	[thread overview]
Message-ID: <CAMuHMdXK6dVfMhMTepr2cfVfDVaLpoA9vPn-c=FNkM0dmxin9A@mail.gmail.com> (raw)
In-Reply-To: <4677994.NrntHOKO7A@wuerfel>

Hi Arnd,

On Mon, Mar 9, 2015 at 3:10 PM, Arnd Bergmann <arnd@arndb.de> wrote:
>> smc91x fallout. The lpd270_defconfig failure looks like not covered by
>> "ARM: fix typos in smc91x platform data" yet?
>
> It's not?
>
> This should be part of that patch:
>
> --- a/arch/arm/mach-pxa/lpd270.c
> +++ b/arch/arm/mach-pxa/lpd270.c
> @@ -195,7 +195,7 @@ static struct resource smc91x_resources[] = {
>  };
>
>  struct smc91x_platdata smc91x_platdata = {
> -       .flags = SMC91X_USE_16BIT | SMC91X_NOWAIT;
> +       .flags = SMC91X_USE_16BIT | SMC91X_NOWAIT,

Ah OK. Sorry, I thought there was a different reason.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

      reply	other threads:[~2015-03-09 14:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1425898222-19721-1-git-send-email-geert@linux-m68k.org>
2015-03-09 10:56 ` Build regressions/improvements in v4.0-rc3 Geert Uytterhoeven
2015-03-09 14:10   ` Arnd Bergmann
2015-03-09 14:27     ` Geert Uytterhoeven [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='CAMuHMdXK6dVfMhMTepr2cfVfDVaLpoA9vPn-c=FNkM0dmxin9A@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@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).