linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: stats (Was: Linux 6.6-rc1)
Date: Mon, 11 Sep 2023 11:02:03 +0200 (CEST)	[thread overview]
Message-ID: <2b3f3296-5263-1746-1f4-d0ad95a52922@linux-m68k.org> (raw)
In-Reply-To: <20230911123839.7ab72f81@canb.auug.org.au>

 	Hi Stephen,

On Mon, 11 Sep 2023, Stephen Rothwell wrote:
> There are also 275 commits in next-20230828 that didn't make it into
> v6.6-rc1.

> Top ten commiters:
>
>     11 geert+renesas@glider.be

Thanks for your report!

I had a look, and this was caused due to me rebasing
renesas-dts-for-v6.6 on top of renesas-fixes-for-v6.5, but forgetting to
recreate renesas/next afterwards (there were no conflicts).  So all
eleven commits did make it upstream.

Gr{oetje,eeting}s,

 						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
 							    -- Linus Torvalds

  reply	other threads:[~2023-09-11 21:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-10 23:53 Linux 6.6-rc1 Linus Torvalds
2023-09-11  2:38 ` linux-next: stats (Was: Linux 6.6-rc1) Stephen Rothwell
2023-09-11  9:02   ` Geert Uytterhoeven [this message]
2023-09-11  8:38 ` Build regressions/improvements in v6.6-rc1 Geert Uytterhoeven
2023-09-11 23:08   ` Randy Dunlap
2023-09-12  6:49     ` Geert Uytterhoeven
2023-09-12  7:33       ` Randy Dunlap
2023-09-12  6:39   ` Geert Uytterhoeven
2023-09-12 17:59 ` Linux 6.6-rc1 Guenter Roeck
2023-09-12 18:17   ` Linus Torvalds
2023-09-12 18:25     ` Helge Deller
2023-09-12 18:33     ` Guenter Roeck

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=2b3f3296-5263-1746-1f4-d0ad95a52922@linux-m68k.org \
    --to=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.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).