From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: Greg KH <gregkh@linuxfoundation.org>, James Clark <james.clark@arm.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Coresight ML <coresight@lists.linaro.org>
Subject: Re: [PATCH v4 1/4] devres: Provide krealloc_array
Date: Wed, 31 May 2023 23:44:55 +0100 [thread overview]
Message-ID: <46bb773c-31a8-c57a-0cde-39c27d0a6e36@arm.com> (raw)
In-Reply-To: <2023051530-immunize-pony-49ef@gregkh>
(Removed irrelevant recipients), +Cc: coresight ml
Hi Greg,
On 15/05/2023 12:55, Greg KH wrote:
> On Mon, May 15, 2023 at 08:55:33AM +0100, James Clark wrote:
>>
>>
>> On 13/05/2023 12:04, Greg KH wrote:
>>> On Tue, May 09, 2023 at 10:49:38AM +0100, James Clark wrote:
>>>> There is no krealloc_array equivalent in devres. Users would have to
>>>> do their own multiplication overflow check so provide one.
>>>>
>>>> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>>>> Signed-off-by: James Clark <james.clark@arm.com>
>>>> ---
>>>> Documentation/driver-api/driver-model/devres.rst | 1 +
>>>> include/linux/device.h | 11 +++++++++++
>>>> 2 files changed, 12 insertions(+)
...
>> Maybe something could be done with some macro magic, but it would
>> probably end up being worse than just copying them and would affect the
>> real ones as well. So yeah I can't think of any easy gains either.
>
> Ok, that's good. Given a lack of objections from others, I'll just take
> this through my driver core tree in a few days.
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).
Kind regards
Suzuki
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-05-31 22:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230509094942.396150-1-james.clark@arm.com>
[not found] ` <20230509094942.396150-2-james.clark@arm.com>
[not found] ` <2023051340-sinuous-darkroom-2497@gregkh>
[not found] ` <89ad5070-db72-7bf1-5d86-a89fea54e789@arm.com>
2023-05-15 11:55 ` [PATCH v4 1/4] devres: Provide krealloc_array Greg KH
2023-05-31 22:44 ` Suzuki K Poulose [this message]
2023-05-31 22:47 ` Suzuki K Poulose
2023-06-01 9:33 ` Greg KH
2023-06-01 9:52 ` Suzuki K Poulose
2023-06-05 13:39 ` Suzuki K Poulose
2023-06-05 15:20 ` Greg KH
2023-06-05 15:59 ` Suzuki K Poulose
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=46bb773c-31a8-c57a-0cde-39c27d0a6e36@arm.com \
--to=suzuki.poulose@arm.com \
--cc=coresight@lists.linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=james.clark@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).