From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Howard Yen <howardyen@google.com>
Cc: gregkh@linuxfoundation.org, rafael@kernel.org,
mathias.nyman@intel.com, hch@lst.de, m.szyprowski@samsung.com,
robin.murphy@arm.com, petr.tesarik.ext@huawei.com,
broonie@kernel.org, james@equiv.tech, james.clark@arm.com,
masahiroy@kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, iommu@lists.linux.dev
Subject: Re: [PATCH v5 0/2] Add support for multiple coherent memory regions
Date: Mon, 11 Mar 2024 12:32:54 +0200 [thread overview]
Message-ID: <Ze7d1rrZsQZdDVQH@smile.fi.intel.com> (raw)
In-Reply-To: <CAJDAHvbRSm_UYgx0fE7o2dJqcBfBbcFR4DrnVydkwfxGo0O4Rg@mail.gmail.com>
On Mon, Mar 11, 2024 at 06:10:47PM +0800, Howard Yen wrote:
> On Mon, Mar 11, 2024 at 6:03 PM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> > On Mon, Mar 11, 2024 at 09:49:45AM +0000, Howard Yen wrote:
...
> > > Changes in v5:
> > > - Fix build break.
> > > - Use of_property_count_u32_elems() instead of
> > > of_property_count_elems_of_size().
> >
> > Have you tried to use --histogram diff algo?
>
> Yes, I used the below command to create the patch v5.
> `git format-patch --cover-letter --histogram -v5 51b70ff55`
Thank you for confirming!
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2024-03-11 10:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 9:49 [PATCH v5 0/2] Add support for multiple coherent memory regions Howard Yen
2024-03-11 9:49 ` [PATCH v5 1/2] dma-coherent: add support for multi coherent rmems per dev Howard Yen
2024-03-11 9:49 ` [PATCH v5 2/2] usb: host: xhci-plat: add support for multi memory regions Howard Yen
2024-03-11 12:21 ` Robin Murphy
2024-03-13 7:12 ` Dan Carpenter
2024-03-11 10:03 ` [PATCH v5 0/2] Add support for multiple coherent " Andy Shevchenko
2024-03-11 10:10 ` Howard Yen
2024-03-11 10:32 ` Andy Shevchenko [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=Ze7d1rrZsQZdDVQH@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=howardyen@google.com \
--cc=iommu@lists.linux.dev \
--cc=james.clark@arm.com \
--cc=james@equiv.tech \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=masahiroy@kernel.org \
--cc=mathias.nyman@intel.com \
--cc=petr.tesarik.ext@huawei.com \
--cc=rafael@kernel.org \
--cc=robin.murphy@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.