All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Li <philip.li@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [linux-stable-rc:queue/5.4 109/220] /tmp/filter-273424.s:50187: Error: bad expression
Date: Thu, 09 Jul 2020 08:26:35 +0800	[thread overview]
Message-ID: <20200709002634.GB12731@intel.com> (raw)
In-Reply-To: <CAKwvOd=_PUTQWZ7bOvFqaQKqPaVPnL11uG5iC96K9Hf-3yDGoQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1806 bytes --]

On Wed, Jul 08, 2020 at 11:13:13AM -0700, Nick Desaulniers wrote:
> On Tue, Jul 7, 2020 at 6:29 PM Philip Li <philip.li@intel.com> wrote:
> >
> > On Tue, Jul 07, 2020 at 10:01:12AM -0700, Nick Desaulniers wrote:
> > > Looks like c4e5c229b610, should we ask stable to backport to 5.4?  I
> > > don't think we had clang builds working for 5.4 for s390, so maybe we
> > > should just Philip to disable Clang builds of this stable branch for
> > > s390? (There may not be too many backports to support, but I don't
> > Got it, we will disable s390 for the linux-stable-rc.
> 
> Yeah, it's hard for s390 and probably riscv support on stable as we
> only got those working on mainline recently.
got it, we will disable riscv for stable as well when kernel <= 5.4.

> 
> > BTW: does the bot need switch to use clang's as instead of gnu's?
> 
> No; in the process of whipping LLVM's binutils substitutes into shape,
> we're doing pretty well, except for clang's integrated assembler (IA).
> Ironically, right now we can only build risc-v with clang's IA.
> 
> I would recommend `make LLVM=1` for most cases, though `make CC=clang
> LD=ld.lld ...` may be all that we can get away with for testing stable
> tree's branches.
> 
> Will you, Rong, and the rest of the 0day bot team be attending Linux
> Plumbers Conference this year?  I would like to put together a session
> on "CI and Clang" with the kernelci folks and tuxbuild folks to go
> over our current compatibility table, which is a little complex ATM.
> If you're attending the conference, would you be interested in
> attending such a session?
thanks, this is not decided yet at our side, we will update this later.
Yes, if we have chance to attend, we are glad to join such session.

> -- 
> Thanks,
> ~Nick Desaulniers

  reply	other threads:[~2020-07-09  0:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200707023303.GA277193@ubuntu-s3-xlarge-x86>
2020-07-07 17:01 ` [linux-stable-rc:queue/5.4 109/220] /tmp/filter-273424.s:50187: Error: bad expression Nick Desaulniers
2020-07-08  1:29   ` Philip Li
2020-07-08 18:13     ` Nick Desaulniers
2020-07-09  0:26       ` Philip Li [this message]
2020-07-06  7:19 kernel test robot
2020-07-06  8:27 ` Wolfram Sang
2020-07-06 17:01 ` Nick Desaulniers

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=20200709002634.GB12731@intel.com \
    --to=philip.li@intel.com \
    --cc=kbuild-all@lists.01.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 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.