All of lore.kernel.org
 help / color / mirror / Atom feed
From: Curtis Malainey <cujomalainey@google.com>
To: Guenter Roeck <groeck@google.com>
Cc: Takashi Iwai <tiwai@suse.de>,
	alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
	Dylan Reid <dgreid@google.com>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: Cannot build broadwell on for-5.3
Date: Tue, 28 May 2019 09:21:16 -0700	[thread overview]
Message-ID: <CAOReqxgVdnkfst3Nabr6pFRrmeOmxVquPNjUHx4XtxQ3KY=afg@mail.gmail.com> (raw)
In-Reply-To: <CABXOdTePNR=O0EhUgFNVCUvCbqaKtpdnZw=NtFLc6aNtAWUpKg@mail.gmail.com>

On Mon, May 27, 2019 at 10:24 AM Guenter Roeck <groeck@google.com> wrote:
>
> FWIW, the Linux kernel still officially supports our version of gcc
> (4.9.4, I believe). "Your version of gcc is too old" is not a good
> argument to make.
>
> Guenter
>
IIRC, we are running modified 4.9.2, stock 4.9.2 works fine but for
some reason ours doesn't. It was not a "this is broken and that is
that" it was more a "oh, this is the issue, I am going to take this
offline now." I am in contact with the author who broke us who happens
to be another googler and he is looking into what is going on. The
short term fix is to revert 392bef709659abea614abfe53cf228e7a59876a4
on whatever branch you are working on.

Curtis

      reply	other threads:[~2019-05-28 16:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-21 23:37 Cannot build broadwell on for-5.3 Curtis Malainey
2019-05-22 14:44 ` Takashi Iwai
2019-05-22 15:21   ` Pierre-Louis Bossart
2019-05-22 18:30     ` Curtis Malainey
2019-05-27 17:24       ` Guenter Roeck
2019-05-28 16:21         ` Curtis Malainey [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='CAOReqxgVdnkfst3Nabr6pFRrmeOmxVquPNjUHx4XtxQ3KY=afg@mail.gmail.com' \
    --to=cujomalainey@google.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=dgreid@google.com \
    --cc=groeck@google.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=tiwai@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.