From: Greg KH <gregkh@linuxfoundation.org>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: James Clark <james.clark@arm.com>,
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: Mon, 5 Jun 2023 17:20:36 +0200 [thread overview]
Message-ID: <2023060546-deputy-geriatric-2706@gregkh> (raw)
In-Reply-To: <6cbdce5c-d470-9717-774d-2d25c9fc24c1@arm.com>
On Mon, Jun 05, 2023 at 02:39:44PM +0100, Suzuki K Poulose wrote:
> 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
Looks good to me!
_______________________________________________
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-06-05 15:21 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
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 [this message]
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=2023060546-deputy-geriatric-2706@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=coresight@lists.linaro.org \
--cc=james.clark@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=suzuki.poulose@arm.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