All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Gabor Juhos <j4g8y7@gmail.com>
Cc: Georgi Djakov <djakov@kernel.org>,
	Raviteja Laggyshetty <quic_rlaggysh@quicinc.com>,
	Johan Hovold <johan+linaro@kernel.org>,
	Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
	linux-pm@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] interconnect: avoid memory allocation when 'icc_bw_lock' is held
Date: Fri, 27 Jun 2025 11:43:27 +0200	[thread overview]
Message-ID: <aF5nv6TQoyfh7wKS@hovoldconsulting.com> (raw)
In-Reply-To: <b960680d-6c5a-4130-b2dd-4ddf1f800430@gmail.com>

On Fri, Jun 27, 2025 at 11:36:26AM +0200, Gabor Juhos wrote:
> 2025. 06. 27. 9:11 keltezéssel, Johan Hovold írta:
> > On Thu, Jun 26, 2025 at 05:00:42PM +0200, Gabor Juhos wrote:

> >> Despite the note above, your proposal looks good to me. Would you like to
> >> send it as a formal patch, or shall I do it?
> > 
> > I can post it in a bit.
> 
> Great, just saw the final patch. Thank you!

Here it is for reference:

	https://lore.kernel.org/lkml/20250627075854.26943-1-johan+linaro@kernel.org/

It looks like Georgi picked up the patch from this thread yesterday,
which should be fine as well as I only changed the commit message
(replacing the ipc splat with one from sc8280xp) before posting it as
v4.

Johan

  reply	other threads:[~2025-06-27  9:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-25 11:25 [PATCH v3] interconnect: avoid memory allocation when 'icc_bw_lock' is held Gabor Juhos
2025-06-25 12:30 ` Johan Hovold
2025-06-25 12:41   ` Johan Hovold
2025-06-25 13:15     ` Gabor Juhos
2025-06-25 14:02       ` Johan Hovold
2025-06-25 15:35         ` Gabor Juhos
2025-06-26  9:30           ` Johan Hovold
2025-06-26 15:00             ` Gabor Juhos
2025-06-27  7:11               ` Johan Hovold
2025-06-27  9:36                 ` Gabor Juhos
2025-06-27  9:43                   ` Johan Hovold [this message]
2025-06-27 12:23                     ` Gabor Juhos

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=aF5nv6TQoyfh7wKS@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=bryan.odonoghue@linaro.org \
    --cc=djakov@kernel.org \
    --cc=j4g8y7@gmail.com \
    --cc=johan+linaro@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=quic_rlaggysh@quicinc.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.