All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Jon Hunter <jonathanh@nvidia.com>,
	Stefan Wahren <stefan.wahren@i2se.com>,
	miles.chen@mediatek.com, Jisheng Zhang <jszhang@kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	Palmer Dabbelt <palmerdabbelt@google.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: linux-tegra@vger.kernel.org
Subject: Re: Build error: ‘EM_RISCV’ undeclared
Date: Fri, 24 Sep 2021 12:42:31 -0700	[thread overview]
Message-ID: <d3c8b3a4-6881-f882-3af8-1aa3a28f60c0@infradead.org> (raw)
In-Reply-To: <bcf57e67-98e2-b4b1-cb62-a2d2829df142@nvidia.com>

On 9/24/21 12:01 PM, Jon Hunter wrote:
> 
> On 24/09/2021 19:05, Stefan Wahren wrote:
>> Hi,
>>
>> Am 24.09.21 um 14:55 schrieb Jon Hunter:
>>>
>>>
>>> On 24/09/2021 13:15, miles.chen@mediatek.com wrote:
>>>> From: Jon Hunter <jonathanh@nvidia.com>
>>>>
>>>>
>>>>> This is still broken in the mainline. Any plans to get this fix
>>>>> merged there? I believe it has now been broken for nearly 2 weeks.
>>>>
>>>> the fix [1] is in linux-next now, thanks.

so who merged the patch [1] into linux-next?  Andrew?

Seems to me that Andrew should be cc-ed here [added].


>>> Yes I know that. However, we need it in the mainline. It has been
>>> broken for nearly 2 weeks now and all our automation for mainline is
>>> not running because we cannot build. Please get this fix into mainline
>>> as soon as possible.
>>
>> as stated in [1], you can try to update you build environment.
> 
> These are farm build machines so not that easy or quick to update. Given the change that introduced the breakage is in the mainline, the fix also need to be merged into the mainline. Otherwise we need to revert the initial change.

Yes.

-- 
~Randy

      reply	other threads:[~2021-09-24 19:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-12 10:29 Build error: ‘EM_RISCV’ undeclared Stefan Wahren
2021-09-13  2:49 ` Miles Chen
2021-09-24  9:30   ` Jon Hunter
2021-09-24 12:55     ` Jon Hunter
2021-09-24 18:05       ` Stefan Wahren
2021-09-24 19:01         ` Jon Hunter
2021-09-24 19:42           ` Randy Dunlap [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=d3c8b3a4-6881-f882-3af8-1aa3a28f60c0@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=jonathanh@nvidia.com \
    --cc=jszhang@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=miles.chen@mediatek.com \
    --cc=palmerdabbelt@google.com \
    --cc=stefan.wahren@i2se.com \
    /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.