From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Mark Brown <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 Mar 9
Date: Mon, 9 Mar 2026 20:51:01 +0100 [thread overview]
Message-ID: <aa8kpRLIdvA98N-J@black.igk.intel.com> (raw)
In-Reply-To: <aa8WV_KvEV_TFPPZ@sirena.org.uk>
On Mon, Mar 09, 2026 at 06:49:59PM +0000, Mark Brown wrote:
> Hi all,
>
> Changes since 20260306:
The 20260309 contains a file (some bug?) of more than 1GiB in size with interesting name:
": change inode->i_ino from unsigned long to u64" (without surrounding double quotes).
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/
Mode Name Size
-rw-r--r-- .clang-format 24291 logstatsplain
-rw-r--r-- .clippy.toml 374 logstatsplain
-rw-r--r-- .cocciconfig 59 logstatsplain
-rw-r--r-- .editorconfig 566 logstatsplain
-rw-r--r-- .get_maintainer.ignore 270 logstatsplain
-rw-r--r-- .gitattributes 105 logstatsplain
-rw-r--r-- .gitignore 2238 logstatsplain
-rw-r--r-- .mailmap 54433 logstatsplain
-rw-r--r-- .pylintrc 66 logstatsplain
-rw-r--r-- .rustfmt.toml 369 logstatsplain
-rw-r--r-- : change inode->i_ino from unsigned long to u64 1173300385 logstatsplain
-rw-r--r-- COPYING 496 logstatsplain
-rw-r--r-- CREDITS 107693 logstatsplain
...
Please, drop this stuff, and remake the tag.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-03-09 19:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 18:49 linux-next: Tree for Mar 9 Mark Brown
2026-03-09 19:51 ` Andy Shevchenko [this message]
2026-03-09 19:52 ` Mark Brown
2026-03-09 21:53 ` Randy Dunlap
2026-03-10 3:50 ` linux-next: Tree for Mar 9 (ntfs) Randy Dunlap
2026-03-10 4:05 ` Namjae Jeon
-- strict thread matches above, loose matches on Subject: below --
2023-03-09 1:46 linux-next: Tree for Mar 9 Stephen Rothwell
2022-03-09 11:53 Stephen Rothwell
2021-03-09 3:56 Stephen Rothwell
2018-03-09 4:30 Stephen Rothwell
2018-03-09 5:07 ` Stephen Rothwell
2017-03-09 2:45 Stephen Rothwell
2016-03-09 5:38 Stephen Rothwell
2012-03-09 8:11 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=aa8kpRLIdvA98N-J@black.igk.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