The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Lukasz Luba <lukasz.luba@arm.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Xuewen Yan <xuewen.yan94@gmail.com>,
	Xuewen Yan <xuewen.yan@unisoc.com>,
	rafael@kernel.org, pavel@kernel.org, lenb@kernel.org,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	ke.wang@unisoc.com
Subject: Re: [RFC PATCH 1/2] PM: EM: Export em_table_alloc/free
Date: Mon, 27 Jul 2026 20:36:16 -0700	[thread overview]
Message-ID: <amgjsFwIQB01NhQZ@infradead.org> (raw)
In-Reply-To: <82e71c8f-7755-43f6-9518-209525f5acbc@arm.com>

On Mon, Jul 27, 2026 at 09:03:04AM +0100, Lukasz Luba wrote:
> It's a bit more complex situation IMHO.

It's not.  And if you think stupid Android decisions that are 100%
contrary to upstream policies should in any way relevant, you should
spend your time on RTOS BSPs and not argue on Linux mailing lists.


  reply	other threads:[~2026-07-28  3:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-10  8:24 [RFC PATCH 1/2] PM: EM: Export em_table_alloc/free Xuewen Yan
2026-07-10  8:24 ` [RFC PATCH 2/2] PM: EM: Validate new_table in em_dev_update_perf_domain() Xuewen Yan
2026-07-10  8:36   ` Lukasz Luba
2026-07-10  8:34 ` [RFC PATCH 1/2] PM: EM: Export em_table_alloc/free Lukasz Luba
2026-07-13  7:34 ` Christoph Hellwig
2026-07-21 11:10   ` Xuewen Yan
     [not found]     ` <amCHAZgQQkgDSQYo@infradead.org>
2026-07-27  8:03       ` Lukasz Luba
2026-07-28  3:36         ` Christoph Hellwig [this message]
2026-07-28  8:07           ` Lukasz Luba
2026-07-28  8:17             ` Christoph Hellwig

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=amgjsFwIQB01NhQZ@infradead.org \
    --to=hch@infradead.org \
    --cc=ke.wang@unisoc.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lukasz.luba@arm.com \
    --cc=pavel@kernel.org \
    --cc=rafael@kernel.org \
    --cc=xuewen.yan94@gmail.com \
    --cc=xuewen.yan@unisoc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox