mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Davis <afd@ti.com>
To: Jiri Slaby <jirislaby@kernel.org>, Christoph Hellwig <hch@lst.de>,
	<jassisinghbrar@gmail.com>
Cc: <stefani@seibold.net>, <gregkh@linuxfoundation.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] kfifo: don't include dma-mapping.h in kfifo.h
Date: Wed, 23 Oct 2024 12:01:30 -0500	[thread overview]
Message-ID: <abc0dce9-b64f-451e-8315-ef9e39d0503b@ti.com> (raw)
In-Reply-To: <33b28b0a-b19d-459a-8db4-678df60cd799@kernel.org>

On 10/23/24 1:30 AM, Jiri Slaby wrote:
> On 23. 10. 24, 7:53, Christoph Hellwig wrote:
>> Nothing in kfifo.h directly needs dma-mapping.h, only two macros
>> use DMA_MAPPING_ERROR when actually instantiated.  Drop the
>> dma-mapping.h include to reduce include bloat.
>>
>> Add an explicity <linux/io.h> include to drivers/mailbox/omap-mailbox.c
>> as that file uses __raw_readl and __raw_writel through a complicated
>> include chain involving <linux/dma-mapping.h>
>>
>> Fixes: d52b761e4b1a ("kfifo: add kfifo_dma_out_prepare_mapped()")
>> Signed-off-by: Christoph Hellwig <hch@lst.de>
>> ---
>>
>> Changes since v1:
>>   - improve the commit log
>>
>>   drivers/mailbox/omap-mailbox.c | 1 +
>>   include/linux/kfifo.h          | 1 -
>>   samples/kfifo/dma-example.c    | 1 +
>>   3 files changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/mailbox/omap-mailbox.c b/drivers/mailbox/omap-mailbox.c
>> index 6797770474a5..680243751d62 100644
>> --- a/drivers/mailbox/omap-mailbox.c
>> +++ b/drivers/mailbox/omap-mailbox.c
>> @@ -15,6 +15,7 @@
>>   #include <linux/slab.h>
>>   #include <linux/kfifo.h>
> 
> Funnily enough, this driver does not use kfifo since:
> commit 3f58c1f4206f37d0af4595a9046c76016334b301
> Author: Andrew Davis <afd@ti.com>
> Date:   Wed Apr 10 08:59:42 2024 -0500
> 
>      mailbox: omap: Remove kernel FIFO message queuing
> 
>>   #include <linux/err.h>
>> +#include <linux/io.h>
> 
> So this should have been revealed at that point (while removing kfifo.h in that commit too).
> 
> Perhaps Andrew can remove the include now?
> 

Yes, I'll send a patch dropping kfifo.h (unless you want to just do it
as part of this patch).

The addition of io.h is still correct here as we seem to have been
including it indirectly before, which is always a bit hacky.
So for this patch,

Acked-by: Andrew Davis <afd@ti.com>

> thanks,

      reply	other threads:[~2024-10-23 17:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-23  5:53 Christoph Hellwig
2024-10-23  6:01 ` Greg KH
2024-10-23  6:30 ` Jiri Slaby
2024-10-23 17:01   ` Andrew Davis [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=abc0dce9-b64f-451e-8315-ef9e39d0503b@ti.com \
    --to=afd@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=jassisinghbrar@gmail.com \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefani@seibold.net \
    /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

all inboxes | Powered by JetHome®