linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: Greg KH <gregkh@linuxfoundation.org>
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 16:59:40 +0100	[thread overview]
Message-ID: <ebb09b1b-26ab-48dc-d69f-c7fcbd5d48e8@arm.com> (raw)
In-Reply-To: <2023060546-deputy-geriatric-2706@gregkh>

On 05/06/2023 16:20, Greg KH wrote:
> On Mon, Jun 05, 2023 at 02:39:44PM +0100, Suzuki K Poulose wrote:

>> 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!

Thank you so much for checking ! I will push this to coresight/next.

Suzuki

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2023-06-05 16:00 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
2023-06-05 15:59                   ` Suzuki K Poulose [this message]

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=ebb09b1b-26ab-48dc-d69f-c7fcbd5d48e8@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).