From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: broonie@kernel.org
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Dec 13
Date: Tue, 14 Dec 2021 13:44:26 +0200 [thread overview]
Message-ID: <YbiDmp3bJr9/Uctq@smile.fi.intel.com> (raw)
In-Reply-To: <20211214030215.3181149-1-broonie@kernel.org>
On Tue, Dec 14, 2021 at 03:02:15AM +0000, broonie@kernel.org wrote:
> Hi all,
>
> Non-merge commits (relative to Linus' tree): 5960
> 6555 files changed, 277265 insertions(+), 120864 deletions(-)
Mark, is it possible to add tags to the releases, please?
When you do them tags are missed, I have to add them manually after my scripts
out of a sudden switched from Linux Next base to latest used vanilla tag with
all nice outcomes...
> ----------------------------------------------------------------------------
>
> 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 a defconfig for arm64, an allmodconfig for x86_64, a
> multi_v7_defconfig for arm and a native build of tools/perf.
>
> Below is a summary of the state of the merge.
>
> I am currently merging 346 trees (counting Linus' and 94 trees of bug
> fix patches pending for the current merge release).
>
> Stats about the size of the tree over time can be seen at
> http://neuling.org/linux-next-size.html .
>
> Status of my local build tests will be at
> http://kisskb.ellerman.id.au/linux-next . If maintainers want to give
> advice about cross compilers/configs that work, we are always open to add
> more builds.
>
> Thanks to Randy Dunlap for doing many randconfig builds. And to Paul
> Gortmaker for triage and bug fixes.
>
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-12-14 11:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 3:02 linux-next: Tree for Dec 13 broonie
2021-12-14 6:20 ` linux-next: Tree for Dec 13 (SND_AMD_ACP_CONFIG) Randy Dunlap
2021-12-14 13:51 ` Pierre-Louis Bossart
2021-12-14 16:26 ` Randy Dunlap
2021-12-14 17:21 ` Daniel Baluta
2021-12-14 17:25 ` Pierre-Louis Bossart
2021-12-14 17:40 ` Daniel Baluta
2021-12-14 11:44 ` Andy Shevchenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-13 4:21 linux-next: Tree for Dec 13 Stephen Rothwell
2022-12-13 4:51 Stephen Rothwell
2019-12-13 2:45 Stephen Rothwell
2018-12-13 6:49 Stephen Rothwell
2017-12-13 5:33 Stephen Rothwell
2016-12-13 6:04 Stephen Rothwell
2013-12-13 5:10 Stephen Rothwell
2012-12-13 6:53 Stephen Rothwell
2011-12-13 7:21 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=YbiDmp3bJr9/Uctq@smile.fi.intel.com \
--to=andriy.shevchenko@intel.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).