From: Bagas Sanjaya <bagasdotme@gmail.com>
To: broonie@kernel.org, Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Aug 2
Date: Wed, 3 Aug 2022 08:48:58 +0700 [thread overview]
Message-ID: <d1f90d44-a1e9-7490-f789-f928b85a1d26@gmail.com> (raw)
In-Reply-To: <20220803010326.2814276-1-broonie@kernel.org>
On 8/3/22 08:03, broonie@kernel.org wrote:
> Hi all,
>
> Changes since 20220728:
>
> The hid tree gained a build failure which I fixed up.
>
> The thermal tree gained a build failure, I used the version from 20220728
> instead.
>
> The net-next tree gained a conflict against the net tree.
>
> The kvm tree gained a conflict with the kvms390-fixes tree.
>
> The pinctrl tree gained a build failure for which I reverted a commit.
>
> Non-merge commits (relative to Linus' tree): 12734
> 12594 files changed, 1319236 insertions(+), 278745 deletions(-)
>
> ----------------------------------------------------------------------------
>
> I have created today's linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> (patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you
> are tracking the linux-next tree using git, you should not use "git pull"
> to do so as that will try to merge the new linux-next release with the
> old one. You should use "git fetch" and checkout or reset to the new
> master.
>
> You can see which trees have been included by looking in the Next/Trees
> file in the source. There are also quilt-import.log and merge.log
> files in the Next directory. Between each merge, the tree was built
> with an arm64 defconfig, an allmodconfig build for x86_64, a
> multi_v7_defconfig for arm and a native (arm64) build of tools/perf.
>
Hi broonie,
Thanks for keeping linux-next up while Stephen is on vacation.
What is missing here is powerpc build (ppc64_defconfig), since the
architecture is often used for cross-compile test.
And I think since we're at merge window for 6.0, we need to say
"Please do not add material for 6.1 until 6.0-rc1 have been
released".
Thanks.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-08-03 1:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 1:03 linux-next: Tree for Aug 2 broonie
2022-08-03 1:48 ` Bagas Sanjaya [this message]
2022-08-03 11:51 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2023-08-02 4:24 Stephen Rothwell
2021-08-03 1:24 Mark Brown
2019-08-02 5:52 Stephen Rothwell
2018-08-02 9:31 Stephen Rothwell
2017-08-02 6:38 Stephen Rothwell
2016-08-02 4:06 Stephen Rothwell
2013-08-02 8:04 Stephen Rothwell
2012-08-02 4:15 Stephen Rothwell
2011-08-02 5:57 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=d1f90d44-a1e9-7490-f789-f928b85a1d26@gmail.com \
--to=bagasdotme@gmail.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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).