From: Christoph Hellwig <hch@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
uclinux-h8-devel@lists.sourceforge.jp
Subject: is arch/h8300 dead, was Re: linux-next: stats (Was: Linux 5.16-rc1)
Date: Mon, 15 Nov 2021 10:02:21 -0800 [thread overview]
Message-ID: <YZKgrSNXR87q2HSD@infradead.org> (raw)
In-Reply-To: <20211115141718.0ce3947d@canb.auug.org.au>
On Mon, Nov 15, 2021 at 02:17:18PM +1100, Stephen Rothwell wrote:
> There are also 424 commits in next-20211101 that didn't make it into
> v5.16-rc1.
>
> Top ten first word of commit summary:
>
> 53 bluetooth
> 37 tools
> 23 rcu
> 21 drm
> 18 arm
> 17 iio
> 13 soc
> 10 h8300
At least two of the h8300 ones also were in linux-next for the previous
merge window and didn't make it (my set_fs removal patches). What is
the maintainer status of h8300 when nothing gets sent on to Linus?
next prev parent reply other threads:[~2021-11-16 1:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-14 22:28 Linux 5.16-rc1 Linus Torvalds
2021-11-15 3:17 ` linux-next: stats (Was: Linux 5.16-rc1) Stephen Rothwell
2021-11-15 18:02 ` Christoph Hellwig [this message]
2021-11-15 4:56 ` Linux 5.16-rc1 Guenter Roeck
2021-11-15 5:21 ` Linus Torvalds
2021-11-15 6:33 ` Guenter Roeck
2021-11-15 17:07 ` Guenter Roeck
2021-11-15 17:53 ` Linus Torvalds
2021-11-15 20:39 ` Nick Terrell
2021-11-15 18:10 ` Linus Torvalds
2021-11-15 18:19 ` Helge Deller
2021-11-15 18:38 ` Guenter Roeck
2021-11-16 11:36 ` Michael Ellerman
2021-11-16 14:50 ` Guenter Roeck
2021-11-17 20:18 ` Geert Uytterhoeven
2021-11-17 23:29 ` Anton Altaparmakov
2021-11-18 0:28 ` Linus Torvalds
2021-11-18 1:26 ` Anton Altaparmakov
2021-11-18 1:54 ` Linus Torvalds
2021-11-18 21:23 ` Guenter Roeck
2021-11-18 22:34 ` Linus Torvalds
2021-11-18 23:08 ` Guenter Roeck
2021-11-15 16:14 ` Geert Uytterhoeven
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=YZKgrSNXR87q2HSD@infradead.org \
--to=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
--cc=uclinux-h8-devel@lists.sourceforge.jp \
--cc=ysato@users.sourceforge.jp \
/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).