From: Andrew Davis <afd@ti.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Christian Gmeiner <christian.gmeiner@gmail.com>,
John Stultz <jstultz@google.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Sumit Semwal <sumit.semwal@linaro.org>,
<linux-media@vger.kernel.org>, <dri-devel@lists.freedesktop.org>,
<linaro-mm-sig@lists.linaro.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] misc: sram: Add DMA-BUF Heap exporting of SRAM areas
Date: Wed, 2 Aug 2023 11:33:16 -0500 [thread overview]
Message-ID: <a3764397-ec79-0bb6-e3f4-179f92e1e45c@ti.com> (raw)
In-Reply-To: <2023071344-skinhead-send-33f7@gregkh>
On 7/13/23 2:27 PM, Greg Kroah-Hartman wrote:
> On Thu, Jul 13, 2023 at 02:13:16PM -0500, Andrew Davis wrote:
>> +int sram_add_dma_heap(struct sram_dev *sram,
>> + struct sram_reserve *block,
>> + phys_addr_t start,
>> + struct sram_partition *part)
>> +{
>> + struct sram_dma_heap *sram_dma_heap;
>> + struct dma_heap_export_info exp_info;
>> +
>> + dev_info(sram->dev, "Exporting SRAM Heap '%s'\n", block->label);
>
> When drivers are working properly, they are quiet.
>
This should only be printed once in early boot when the memory is added,
I was wanting this to match the other memory exporters/output at the
beginning of boot logs.
But quiet is fine too, will change this to dev_dbg() for v4.
Thanks,
Andrew
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2023-08-02 16:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 19:13 [PATCH v3] misc: sram: Add DMA-BUF Heap exporting of SRAM areas Andrew Davis
2023-07-13 19:27 ` Greg Kroah-Hartman
2023-08-02 16:33 ` Andrew Davis [this message]
2023-07-13 19:28 ` Greg Kroah-Hartman
2023-07-14 7:45 ` [Linaro-mm-sig] " Christian König
2023-08-17 13:13 ` Robin Murphy
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=a3764397-ec79-0bb6-e3f4-179f92e1e45c@ti.com \
--to=afd@ti.com \
--cc=arnd@arndb.de \
--cc=christian.gmeiner@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=jstultz@google.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=sumit.semwal@linaro.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