From: Joel Stanley <joel@jms.id.au> To: SoC Team <soc@kernel.org>, Linux ARM <linux-arm-kernel@lists.infradead.org> Cc: Andrew Jeffery <andrew@aj.id.au>, Zev Weiss <zev@bewilderbeest.net> Subject: [GIT PULL] aspeed: Maintainers updates for v6.6 Date: Tue, 26 Sep 2023 11:21:27 +0000 [thread overview] Message-ID: <CACPK8Xc+D=YBc2Dhk-6-gOuvKN0xGgZYNop6oJVa=VNgaEYOHw@mail.gmail.com> (raw) Hi Arnd, Can we get these merged for 6.6? It's not critical, but best to have the correct information in place sooner rather than later. The following changes since commit 0bb80ecc33a8fb5a682236443c1e740d5c917d1d: Linux 6.6-rc1 (2023-09-10 16:28:41 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/joel/bmc.git tags/aspeed-6.6-maintainers for you to fetch changes up to 9c888dbf2164e320e63f3ebfd85a99486bee9c3a: MAINTAINERS: aspeed: Update Andrew's email address (2023-09-26 20:43:49 +0930) ---------------------------------------------------------------- ASPEED Maintainers update Andrew has changed addresses and the git tree has long since been at a different location. ---------------------------------------------------------------- Andrew Jeffery (1): MAINTAINERS: aspeed: Update Andrew's email address Zev Weiss (1): MAINTAINERS: aspeed: Update git tree URL MAINTAINERS | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Joel Stanley <joel@jms.id.au> To: SoC Team <soc@kernel.org>, Linux ARM <linux-arm-kernel@lists.infradead.org> Cc: Andrew Jeffery <andrew@aj.id.au>, Zev Weiss <zev@bewilderbeest.net> Subject: [GIT PULL] aspeed: Maintainers updates for v6.6 Date: Tue, 26 Sep 2023 11:21:27 +0000 [thread overview] Message-ID: <CACPK8Xc+D=YBc2Dhk-6-gOuvKN0xGgZYNop6oJVa=VNgaEYOHw@mail.gmail.com> (raw) Hi Arnd, Can we get these merged for 6.6? It's not critical, but best to have the correct information in place sooner rather than later. The following changes since commit 0bb80ecc33a8fb5a682236443c1e740d5c917d1d: Linux 6.6-rc1 (2023-09-10 16:28:41 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/joel/bmc.git tags/aspeed-6.6-maintainers for you to fetch changes up to 9c888dbf2164e320e63f3ebfd85a99486bee9c3a: MAINTAINERS: aspeed: Update Andrew's email address (2023-09-26 20:43:49 +0930) ---------------------------------------------------------------- ASPEED Maintainers update Andrew has changed addresses and the git tree has long since been at a different location. ---------------------------------------------------------------- Andrew Jeffery (1): MAINTAINERS: aspeed: Update Andrew's email address Zev Weiss (1): MAINTAINERS: aspeed: Update git tree URL MAINTAINERS | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-09-26 11:21 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-26 11:21 Joel Stanley [this message] 2023-09-26 11:21 ` [GIT PULL] aspeed: Maintainers updates for v6.6 Joel Stanley 2023-09-26 21:03 ` patchwork-bot+linux-soc 2023-09-26 21:21 ` patchwork-bot+linux-soc
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='CACPK8Xc+D=YBc2Dhk-6-gOuvKN0xGgZYNop6oJVa=VNgaEYOHw@mail.gmail.com' \ --to=joel@jms.id.au \ --cc=andrew@aj.id.au \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=soc@kernel.org \ --cc=zev@bewilderbeest.net \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.