[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6cbdce5c-d470-9717-774d-2d25c9fc24c1@arm.com>
Date: Mon, 5 Jun 2023 14:39:44 +0100
From: Suzuki K Poulose <suzuki.poulose@....com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: James Clark <james.clark@....com>, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
Coresight ML <coresight@...ts.linaro.org>
Subject: Re: [PATCH v4 1/4] devres: Provide krealloc_array
Hi Greg
On 01/06/2023 10:52, Suzuki K Poulose wrote:
> On 01/06/2023 10:33, Greg KH wrote:
>> On Wed, May 31, 2023 at 11:44:55PM +0100, Suzuki K Poulose wrote:
>>> (Removed irrelevant recipients), +Cc: coresight ml
...
>>> Apologies for hijacking the thread. We have a series for CoreSight[1]
>>> that depends on this series, which I see that, is queued in your
>>> driver-core-next.
>>>
>>> I would like to queue [1] for the next version (as there are other
>>> work that depend on this, e.g., [2]). Do you have any
>>> recommendations/comments on the proposal ? Are you able to share a
>>> stable branch which can be merged to coresight/next and queue the
>>> series ontop ? (PS: I haven't queued anything for coresight/next yet).
>>
>> You can pull from my driver-core-next branch just fine and assume it
>> will be stable. So just pull in that one commit and all should be good
>> in the future.
>
> Thanks Greg, I will give it a go
Does this look fine with you ?
https://git.kernel.org/pub/scm/linux/kernel/git/coresight/linux.git/log/?h=tmp/devm_krealloc_array
Suzuki
Powered by blists - more mailing lists