From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: Samuel Holland <samuel@sholland.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
rafael.j.wysocki@intel.com
Cc: aou@eecs.berkeley.edu, apatel@ventanamicro.com,
Atish Patra <atishp@rivosinc.com>,
geert@linux-m68k.org, heiko@sntech.de,
kai.heng.feng@canonical.com, mcgrof@kernel.org,
paulmck@kernel.org, Paul Walmsley <paul.walmsley@sifive.com>,
pmladek@suse.com, yuehaibing@huawei.com,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
tangmeng@uniontech.com
Subject: Re: [PATCH 1/3] kernel/reboot: Use the static sys-off handler for any priority
Date: Sun, 19 Feb 2023 02:32:06 +0300 [thread overview]
Message-ID: <0a8358cd-4c2e-ed70-2cc5-1cff27b7594d@collabora.com> (raw)
In-Reply-To: <8bba0d3c-bf10-97df-80a5-ad98d5a417c8@sholland.org>
On 2/19/23 02:20, Samuel Holland wrote:
> On 2/14/23 18:17, Palmer Dabbelt wrote:
...
>> Sorry for being slow here, I'd been assuming someone would Ack this but
>> it looks like maybe there's nobody in the maintainers file for
>> kernel/reboot.c? I'm fine taking this via the RISC-V tree if that's OK
>> with people, but the cover letter suggests the patch is necessary for
>> multiple patch sets.
>
> See also Dmitry's reply[0] to the PSCI thread. (Maybe I should have sent
> both conversions as one series?)
>
> I am happy with the patches going through any tree. The kernel/reboot.c
> patch is exactly the same between the two series, so it should not hurt
> if it gets merged twice. Though if you take this series through the
> RISC-V tree, maybe you want to create a tag for it?
>
> I am not sure exactly what needs to be done here; I am happy to do
> anything that would assist getting both series merged for v6.3, to avoid
> a regression with axp20x[1].
>
> Regards,
> Samuel
>
> [0]:
> https://lore.kernel.org/lkml/0a180849-ba1b-2a82-ab06-ed1b8155d5ca@collabora.com/
> [1]:
> https://lore.kernel.org/lkml/e38d29f5-cd3c-4a2b-b355-2bcfad00a24b@sholland.org/
The reboot.c changes should be acked/applied by Rafael.
I noticed that you haven't CC'd the linux-pm ML, maybe that's why it
hasn't got the attention.
--
Best regards,
Dmitry
WARNING: multiple messages have this Message-ID (diff)
From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: Samuel Holland <samuel@sholland.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
rafael.j.wysocki@intel.com
Cc: aou@eecs.berkeley.edu, apatel@ventanamicro.com,
Atish Patra <atishp@rivosinc.com>,
geert@linux-m68k.org, heiko@sntech.de,
kai.heng.feng@canonical.com, mcgrof@kernel.org,
paulmck@kernel.org, Paul Walmsley <paul.walmsley@sifive.com>,
pmladek@suse.com, yuehaibing@huawei.com,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
tangmeng@uniontech.com
Subject: Re: [PATCH 1/3] kernel/reboot: Use the static sys-off handler for any priority
Date: Sun, 19 Feb 2023 02:32:06 +0300 [thread overview]
Message-ID: <0a8358cd-4c2e-ed70-2cc5-1cff27b7594d@collabora.com> (raw)
In-Reply-To: <8bba0d3c-bf10-97df-80a5-ad98d5a417c8@sholland.org>
On 2/19/23 02:20, Samuel Holland wrote:
> On 2/14/23 18:17, Palmer Dabbelt wrote:
...
>> Sorry for being slow here, I'd been assuming someone would Ack this but
>> it looks like maybe there's nobody in the maintainers file for
>> kernel/reboot.c? I'm fine taking this via the RISC-V tree if that's OK
>> with people, but the cover letter suggests the patch is necessary for
>> multiple patch sets.
>
> See also Dmitry's reply[0] to the PSCI thread. (Maybe I should have sent
> both conversions as one series?)
>
> I am happy with the patches going through any tree. The kernel/reboot.c
> patch is exactly the same between the two series, so it should not hurt
> if it gets merged twice. Though if you take this series through the
> RISC-V tree, maybe you want to create a tag for it?
>
> I am not sure exactly what needs to be done here; I am happy to do
> anything that would assist getting both series merged for v6.3, to avoid
> a regression with axp20x[1].
>
> Regards,
> Samuel
>
> [0]:
> https://lore.kernel.org/lkml/0a180849-ba1b-2a82-ab06-ed1b8155d5ca@collabora.com/
> [1]:
> https://lore.kernel.org/lkml/e38d29f5-cd3c-4a2b-b355-2bcfad00a24b@sholland.org/
The reboot.c changes should be acked/applied by Rafael.
I noticed that you haven't CC'd the linux-pm ML, maybe that's why it
hasn't got the attention.
--
Best regards,
Dmitry
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-02-18 23:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 16:19 [PATCH 0/3] riscv: sbi: Switch to the sys-off handler API Samuel Holland
2022-12-28 16:19 ` Samuel Holland
2022-12-28 16:19 ` [PATCH 1/3] kernel/reboot: Use the static sys-off handler for any priority Samuel Holland
2022-12-28 16:19 ` Samuel Holland
2023-02-15 0:17 ` Palmer Dabbelt
2023-02-15 0:17 ` Palmer Dabbelt
2023-02-18 23:20 ` Samuel Holland
2023-02-18 23:20 ` Samuel Holland
2023-02-18 23:32 ` Dmitry Osipenko [this message]
2023-02-18 23:32 ` Dmitry Osipenko
2023-03-15 3:10 ` Palmer Dabbelt
2023-03-15 3:10 ` Palmer Dabbelt
2022-12-28 16:19 ` [PATCH 2/3] riscv: sbi: Share the code for unsupported extension warnings Samuel Holland
2022-12-28 16:19 ` Samuel Holland
2023-01-03 8:54 ` Geert Uytterhoeven
2023-01-03 8:54 ` Geert Uytterhoeven
2022-12-28 16:19 ` [PATCH 3/3] riscv: sbi: Switch to the sys-off handler API Samuel Holland
2022-12-28 16:19 ` Samuel Holland
2022-12-28 18:30 ` [PATCH 0/3] " Conor Dooley
2022-12-28 18:30 ` Conor Dooley
2023-01-03 10:54 ` Conor Dooley
2023-01-03 10:54 ` Conor Dooley
2023-05-12 21:50 ` Palmer Dabbelt
2023-05-12 21:50 ` Palmer Dabbelt
2023-05-12 21:51 ` Palmer Dabbelt
2023-05-12 21:51 ` Palmer Dabbelt
2023-05-11 20:53 ` Palmer Dabbelt
2023-05-11 20:53 ` Palmer Dabbelt
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=0a8358cd-4c2e-ed70-2cc5-1cff27b7594d@collabora.com \
--to=dmitry.osipenko@collabora.com \
--cc=aou@eecs.berkeley.edu \
--cc=apatel@ventanamicro.com \
--cc=atishp@rivosinc.com \
--cc=geert@linux-m68k.org \
--cc=heiko@sntech.de \
--cc=kai.heng.feng@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mcgrof@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=paulmck@kernel.org \
--cc=pmladek@suse.com \
--cc=rafael.j.wysocki@intel.com \
--cc=samuel@sholland.org \
--cc=tangmeng@uniontech.com \
--cc=yuehaibing@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: link
Be 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.