From: Gregory CLEMENT <gregory.clement@bootlin.com> To: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>, <arm@kernel.org>, soc@kernel.org Cc: Andrew Lunn <andrew@lunn.ch>, Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>, <linux-arm-kernel@lists.infradead.org> Subject: [GIT PULL] ARM: mvebu: fixes for v6.6 (#1) Date: Thu, 19 Oct 2023 17:11:21 +0200 [thread overview] Message-ID: <875y32abqe.fsf@BL-laptop> (raw) Hi, Here is the first pull request for fixes for mvebu for v6.6. Gregory 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/gclement/mvebu.git tags/mvebu-fixes-6.6-1 for you to fetch changes up to 1122a9c2ebe02435014a0f40dcc50f4333286f0f: MAINTAINERS: uDPU: add remaining Methode boards (2023-09-20 11:47:13 +0200) ---------------------------------------------------------------- mvebu fixes for 6.6 (part 1) Update MAINTAINERS for eDPU board ---------------------------------------------------------------- Robert Marko (2): MAINTAINERS: uDPU: make myself maintainer of it MAINTAINERS: uDPU: add remaining Methode boards MAINTAINERS | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) -- Gregory Clement, Bootlin Embedded Linux and Kernel engineering http://bootlin.com
WARNING: multiple messages have this Message-ID (diff)
From: Gregory CLEMENT <gregory.clement@bootlin.com> To: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>, <arm@kernel.org>, soc@kernel.org Cc: Andrew Lunn <andrew@lunn.ch>, Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>, <linux-arm-kernel@lists.infradead.org> Subject: [GIT PULL] ARM: mvebu: fixes for v6.6 (#1) Date: Thu, 19 Oct 2023 17:11:21 +0200 [thread overview] Message-ID: <875y32abqe.fsf@BL-laptop> (raw) Hi, Here is the first pull request for fixes for mvebu for v6.6. Gregory 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/gclement/mvebu.git tags/mvebu-fixes-6.6-1 for you to fetch changes up to 1122a9c2ebe02435014a0f40dcc50f4333286f0f: MAINTAINERS: uDPU: add remaining Methode boards (2023-09-20 11:47:13 +0200) ---------------------------------------------------------------- mvebu fixes for 6.6 (part 1) Update MAINTAINERS for eDPU board ---------------------------------------------------------------- Robert Marko (2): MAINTAINERS: uDPU: make myself maintainer of it MAINTAINERS: uDPU: add remaining Methode boards MAINTAINERS | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) -- Gregory Clement, Bootlin Embedded Linux and Kernel engineering http://bootlin.com _______________________________________________ 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-10-19 15:11 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-19 15:11 Gregory CLEMENT [this message] 2023-10-19 15:11 ` [GIT PULL] ARM: mvebu: fixes for v6.6 (#1) Gregory CLEMENT 2023-10-23 19:30 ` 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=875y32abqe.fsf@BL-laptop \ --to=gregory.clement@bootlin.com \ --cc=andrew@lunn.ch \ --cc=arm@kernel.org \ --cc=arnd@arndb.de \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=olof@lixom.net \ --cc=sebastian.hesselbarth@gmail.com \ --cc=soc@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: 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.