From: cuigaosheng <cuigaosheng1@huawei.com> To: Arnd Bergmann <arnd@arndb.de> Cc: Russell King - ARM Linux <linux@armlinux.org.uk>, Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>, Andrew Lunn <andrew@lunn.ch>, Gregory CLEMENT <gregory.clement@bootlin.com>, Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>, Viresh Kumar <vireshk@kernel.org>, Shiraz Hashim <shiraz.linux.kernel@gmail.com>, SoC Team <soc@kernel.org>, Linus Walleij <linus.walleij@linaro.org>, Ard Biesheuvel <ardb@kernel.org>, Linux ARM <linux-arm-kernel@lists.infradead.org>, "moderated list:ARM/SAMSUNG EXYNOS ARM ARCHITECTURES" <linux-samsung-soc@vger.kernel.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, <gongruiqi1@huawei.com>, <wangweiyang2@huawei.com> Subject: Re: [PATCH -next 0/3] replace open coded VA->PA calculation Date: Tue, 21 Dec 2021 09:41:32 +0800 [thread overview] Message-ID: <dfc25b22-2f66-4404-66c4-44c9c8c3bab4@huawei.com> (raw) In-Reply-To: <CAK8P3a1-0u4VCCfgc7tjmnANM0yr7oUrQX2y-ZSVvZHDN191BQ@mail.gmail.com> > I could apply them directly with the maintainer Acks, but I don't understand > the significance of you sending them now. Is something broken without the > three patches? Are these the only ones missing from Ard's original series, > or is this preparation? Would you expect the patches to get backported to > stable kernels? Thanks for your reply. This is preparation work for arm32 kaslr,and I want to continue to improve the solution based on the work of Ard. These patches are relatively independent, so I submit these patches first. Gaosheng. 在 2021/12/20 23:39, Arnd Bergmann 写道: > On Sat, Dec 18, 2021 at 9:58 AM Gaosheng Cui <cuigaosheng1@huawei.com> wrote: >> These patches replace an open coded calculation to obtain the physical >> address of a far symbol with a call to the new ldr_l etc macro, and they >> belong to the kaslr patch set of arm32. >> >> Reference: https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git/log/?h=arm-kaslr-latest >> >> Ard Biesheuvel (3): >> arm-soc: exynos: replace open coded VA->PA conversions >> arm-soc: mvebu: replace open coded VA->PA conversion >> arm-soc: various: replace open coded VA->PA calculation > Usually these patches should go through the respective platform > maintainer trees, > and from there into the soc tree, but time is a little short here. > > I could apply them directly with the maintainer Acks, but I don't understand > the significance of you sending them now. Is something broken without the > three patches? Are these the only ones missing from Ard's original series, > or is this preparation? Would you expect the patches to get backported to > stable kernels? > > Arnd > .
WARNING: multiple messages have this Message-ID (diff)
From: cuigaosheng <cuigaosheng1@huawei.com> To: Arnd Bergmann <arnd@arndb.de> Cc: Russell King - ARM Linux <linux@armlinux.org.uk>, Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>, Andrew Lunn <andrew@lunn.ch>, Gregory CLEMENT <gregory.clement@bootlin.com>, Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>, Viresh Kumar <vireshk@kernel.org>, Shiraz Hashim <shiraz.linux.kernel@gmail.com>, SoC Team <soc@kernel.org>, Linus Walleij <linus.walleij@linaro.org>, Ard Biesheuvel <ardb@kernel.org>, Linux ARM <linux-arm-kernel@lists.infradead.org>, "moderated list:ARM/SAMSUNG EXYNOS ARM ARCHITECTURES" <linux-samsung-soc@vger.kernel.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, <gongruiqi1@huawei.com>, <wangweiyang2@huawei.com> Subject: Re: [PATCH -next 0/3] replace open coded VA->PA calculation Date: Tue, 21 Dec 2021 09:41:32 +0800 [thread overview] Message-ID: <dfc25b22-2f66-4404-66c4-44c9c8c3bab4@huawei.com> (raw) In-Reply-To: <CAK8P3a1-0u4VCCfgc7tjmnANM0yr7oUrQX2y-ZSVvZHDN191BQ@mail.gmail.com> > I could apply them directly with the maintainer Acks, but I don't understand > the significance of you sending them now. Is something broken without the > three patches? Are these the only ones missing from Ard's original series, > or is this preparation? Would you expect the patches to get backported to > stable kernels? Thanks for your reply. This is preparation work for arm32 kaslr,and I want to continue to improve the solution based on the work of Ard. These patches are relatively independent, so I submit these patches first. Gaosheng. 在 2021/12/20 23:39, Arnd Bergmann 写道: > On Sat, Dec 18, 2021 at 9:58 AM Gaosheng Cui <cuigaosheng1@huawei.com> wrote: >> These patches replace an open coded calculation to obtain the physical >> address of a far symbol with a call to the new ldr_l etc macro, and they >> belong to the kaslr patch set of arm32. >> >> Reference: https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git/log/?h=arm-kaslr-latest >> >> Ard Biesheuvel (3): >> arm-soc: exynos: replace open coded VA->PA conversions >> arm-soc: mvebu: replace open coded VA->PA conversion >> arm-soc: various: replace open coded VA->PA calculation > Usually these patches should go through the respective platform > maintainer trees, > and from there into the soc tree, but time is a little short here. > > I could apply them directly with the maintainer Acks, but I don't understand > the significance of you sending them now. Is something broken without the > three patches? Are these the only ones missing from Ard's original series, > or is this preparation? Would you expect the patches to get backported to > stable kernels? > > Arnd > . _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-12-21 1:41 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-18 8:58 [PATCH -next 0/3] replace open coded VA->PA calculation Gaosheng Cui 2021-12-18 8:58 ` Gaosheng Cui 2021-12-18 8:58 ` [PATCH -next 1/3] arm-soc: exynos: replace open coded VA->PA conversions Gaosheng Cui 2021-12-18 8:58 ` Gaosheng Cui 2021-12-18 8:58 ` [PATCH -next 2/3] arm-soc: mvebu: replace open coded VA->PA conversion Gaosheng Cui 2021-12-18 8:58 ` Gaosheng Cui 2021-12-18 8:58 ` [PATCH -next 3/3] arm-soc: various: replace open coded VA->PA calculation Gaosheng Cui 2021-12-18 8:58 ` Gaosheng Cui 2021-12-20 15:39 ` [PATCH -next 0/3] " Arnd Bergmann 2021-12-20 15:39 ` Arnd Bergmann 2021-12-20 18:06 ` Andrew Lunn 2021-12-20 18:06 ` Andrew Lunn 2021-12-20 18:16 ` Ard Biesheuvel 2021-12-20 18:16 ` Ard Biesheuvel 2021-12-21 1:41 ` cuigaosheng [this message] 2021-12-21 1:41 ` cuigaosheng 2021-12-21 9:15 ` Arnd Bergmann 2021-12-21 9:15 ` Arnd Bergmann 2021-12-22 2:31 ` Linus Walleij 2021-12-22 2:31 ` Linus Walleij 2021-12-22 9:29 ` Ard Biesheuvel 2021-12-22 9:29 ` Ard Biesheuvel 2021-12-24 4:05 ` Linus Walleij 2021-12-24 4:05 ` Linus Walleij
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=dfc25b22-2f66-4404-66c4-44c9c8c3bab4@huawei.com \ --to=cuigaosheng1@huawei.com \ --cc=andrew@lunn.ch \ --cc=ardb@kernel.org \ --cc=arnd@arndb.de \ --cc=gongruiqi1@huawei.com \ --cc=gregory.clement@bootlin.com \ --cc=krzysztof.kozlowski@canonical.com \ --cc=linus.walleij@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-samsung-soc@vger.kernel.org \ --cc=linux@armlinux.org.uk \ --cc=sebastian.hesselbarth@gmail.com \ --cc=shiraz.linux.kernel@gmail.com \ --cc=soc@kernel.org \ --cc=vireshk@kernel.org \ --cc=wangweiyang2@huawei.com \ /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.