From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Lee Jones <lee@kernel•org>
Cc: "Duje Mihanović" <duje.mihanovic@skole•hr>,
"Linux Kernel Mailing List" <linux-kernel@vger•kernel.org>,
"Linux Next Mailing List" <linux-next@vger•kernel.org>
Subject: Re: linux-next: build failure after merge of the backlight tree
Date: Fri, 8 Mar 2024 06:30:00 +1100 [thread overview]
Message-ID: <20240308063000.6fdce0e5@canb.auug.org.au> (raw)
In-Reply-To: <20240307090446.GL86322@google.com>
[-- Attachment #1: Type: text/plain, Size: 714 bytes --]
Hi Lee,
On Thu, 7 Mar 2024 09:04:46 +0000 Lee Jones <lee@kernel•org> wrote:
>
> On Thu, 07 Mar 2024, Lee Jones wrote:
>
> > Right. So you build each tree as its merged?
More or less. I do some batches of merges (since otherwise it just
takes way to long).
> > My assumption was that all things come together in -next?
This is from my daily summary report:
"Between each merge, the tree was built with a ppc64_defconfig
for powerpc, an allmodconfig for x86_64, a multi_v7_defconfig for arm
and a native build of tools/perf."
> Okay, all patches are now shared between both branches.
Thanks.
> Let me know if there is still an issue.
Will do.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-03-07 19:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 2:28 linux-next: build failure after merge of the backlight tree Stephen Rothwell
2024-03-05 0:16 ` Stephen Rothwell
2024-03-05 9:17 ` Lee Jones
2024-03-05 22:55 ` Stephen Rothwell
2024-03-06 3:04 ` Stephen Rothwell
2024-03-07 8:24 ` Lee Jones
2024-03-07 9:04 ` Lee Jones
2024-03-07 19:30 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-05-27 3:11 Stephen Rothwell
2015-05-27 7:45 ` Lee Jones
2010-05-10 2:43 Stephen Rothwell
2010-05-10 5:41 ` Mike Frysinger
2010-05-17 3:32 ` Stephen Rothwell
2010-05-18 15:54 ` Richard Purdie
2010-05-19 0:56 ` Stephen Rothwell
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=20240308063000.6fdce0e5@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=duje.mihanovic@skole$(echo .)hr \
--cc=lee@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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