public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Marc Zyngier <maz@kernel.org>
Cc: "Li, Meng" <Meng.Li@windriver.com>,
	linux-kernel@vger.kernel.org, arnd@arndb.de, "Hao,
	Kexin" <Kexin.Hao@windriver.com>
Subject: Re: [v2][PATCH] Revert "mfd: syscon: Don't free allocated name for regmap_config"
Date: Mon, 22 Feb 2021 09:21:14 +0000	[thread overview]
Message-ID: <20210222092114.GE376568@dell> (raw)
In-Reply-To: <36cc2d810d90237947ad953ebd6b9fb7@kernel.org>

On Mon, 22 Feb 2021, Marc Zyngier wrote:

> Hi Limeng,
> 
> On 2021-02-22 03:45, Li, Meng wrote:
> > Hi Marc&Lee,
> > 
> > Is there any comment on this patch?
> > Could you please help to review this patch so that I can improve it if
> > it still has weakness?
> 
> If you are confident that the root issue has been fixed, no objection
> from me, but I'm not in a position to test it at the moment (the board
> I found the problem on is in a bit of a state).

I'm not keen on flip-flopping this patch in and out of the kernel.
Someone really needs to spend some time to map out the full life-cycle
and propose a (possibly cross-subsystem) solution.

-- 
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2021-02-22  9:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-15  1:50 [v2][PATCH] Revert "mfd: syscon: Don't free allocated name for regmap_config" meng.li
2021-02-22  3:45 ` Li, Meng
2021-02-22  9:12   ` Marc Zyngier
2021-02-22  9:21     ` Lee Jones [this message]
2021-02-22  9:37       ` Li, Meng
2021-03-09  9:43         ` Lee Jones
2021-03-09  9:51           ` Li, Meng
2021-03-09 18:15             ` Lee Jones
2021-03-10  1:41               ` Li, Meng
2021-03-10  8:31                 ` Lee Jones

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=20210222092114.GE376568@dell \
    --to=lee.jones@linaro.org \
    --cc=Kexin.Hao@windriver.com \
    --cc=Meng.Li@windriver.com \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@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: 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