From: Linus Walleij <linus.walleij@linaro.org> To: SoC Team <soc@kernel.org> Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>, arm-soc <arm@kernel.org> Subject: [GIT PULL] IXP4xx updates for v6.2 Date: Mon, 21 Nov 2022 00:00:06 +0100 [thread overview] Message-ID: <CACRpkdYNwyZ1FDM07MkUfYyYGtXFQfy1xP9Utc5+K2+gn_ZW9g@mail.gmail.com> (raw) Hi SoC folks, here are some small updates to IXP4xx for v6.2. Details in the signed tag! Please pull it in. Yours, Linus Walleij The following changes since commit 9abf2313adc1ca1b6180c508c25f22f9395cc780: Linux 6.1-rc1 (2022-10-16 15:36:24 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-nomadik.git tags/ixp4xx-for-v6.2 for you to fetch changes up to dc6e328a8d28e1c0c6e4f19e90cca17bb8fc126b: ARM: ixp4xx: Remove unused static map (2022-11-20 23:47:06 +0100) ---------------------------------------------------------------- IXP4xx patches for v6.2: - Dropped the final static mappings. - Fixed some errors in the MAINTAINERS file. ---------------------------------------------------------------- Linus Walleij (1): ARM: ixp4xx: Remove unused static map Lukas Bulwahn (1): MAINTAINERS: adjust ARM/INTEL IXP4XX ARM ARCHITECTURE to ixp4xx clean-up MAINTAINERS | 2 -- arch/arm/mach-ixp4xx/ixp4xx-of.c | 25 ++++--------------------- 2 files changed, 4 insertions(+), 23 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Linus Walleij <linus.walleij@linaro.org> To: SoC Team <soc@kernel.org> Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>, arm-soc <arm@kernel.org> Subject: [GIT PULL] IXP4xx updates for v6.2 Date: Mon, 21 Nov 2022 00:00:06 +0100 [thread overview] Message-ID: <CACRpkdYNwyZ1FDM07MkUfYyYGtXFQfy1xP9Utc5+K2+gn_ZW9g@mail.gmail.com> (raw) Hi SoC folks, here are some small updates to IXP4xx for v6.2. Details in the signed tag! Please pull it in. Yours, Linus Walleij The following changes since commit 9abf2313adc1ca1b6180c508c25f22f9395cc780: Linux 6.1-rc1 (2022-10-16 15:36:24 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-nomadik.git tags/ixp4xx-for-v6.2 for you to fetch changes up to dc6e328a8d28e1c0c6e4f19e90cca17bb8fc126b: ARM: ixp4xx: Remove unused static map (2022-11-20 23:47:06 +0100) ---------------------------------------------------------------- IXP4xx patches for v6.2: - Dropped the final static mappings. - Fixed some errors in the MAINTAINERS file. ---------------------------------------------------------------- Linus Walleij (1): ARM: ixp4xx: Remove unused static map Lukas Bulwahn (1): MAINTAINERS: adjust ARM/INTEL IXP4XX ARM ARCHITECTURE to ixp4xx clean-up MAINTAINERS | 2 -- arch/arm/mach-ixp4xx/ixp4xx-of.c | 25 ++++--------------------- 2 files changed, 4 insertions(+), 23 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:[~2022-11-20 23:00 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-20 23:00 Linus Walleij [this message] 2022-11-20 23:00 ` [GIT PULL] IXP4xx updates for v6.2 Linus Walleij 2022-11-21 14:52 ` 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=CACRpkdYNwyZ1FDM07MkUfYyYGtXFQfy1xP9Utc5+K2+gn_ZW9g@mail.gmail.com \ --to=linus.walleij@linaro.org \ --cc=arm@kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --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.