From: Jiri Slaby <jirislaby@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: stefani@seibold.net, jassisinghbrar@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kfifo: don't include dma-mapping.h in kfifo.h
Date: Tue, 15 Oct 2024 09:53:52 +0200 [thread overview]
Message-ID: <7f723486-237f-47d2-b9c1-e5312876dfb5@kernel.org> (raw)
In-Reply-To: <20241015074043.GB24501@lst.de>
On 15. 10. 24, 9:40, Christoph Hellwig wrote:
> On Tue, Oct 15, 2024 at 09:38:24AM +0200, Jiri Slaby wrote:
>> On 14. 10. 24, 16:46, Christoph Hellwig wrote:
>>> Nothing in kfifo.h needs dma-mapping.h. Drop the include to
>>> reduce include bloat.
>>
>> Except DMA_MAPPING_ERROR.
>
> DMA_MAPPING_ERROR is never used by kfifo.h itself. It is used
> by user of the header that instanciate one of the macros that use
> it.
Well, I don't understand. Looking at:
#define kfifo_dma_in_prepare(fifo, sgl, nents, len) \
kfifo_dma_in_prepare_mapped(fifo, sgl, nents, len,
DMA_MAPPING_ERROR)
You'd have to include dma-mapping.h if you used this macro. Even though
you do not explicitly use any other def from the dma header.
I know one will very likely include dma-mapping.h when using the macro.
But that might not be a rule.
>> The header should stay self-contained.
>
> It does with this patch. You can include it as the only header
> in a source file and will work fine. I've actually tried that.
Well, this is not a definition of self-containment. If you use every
macro from a header and it does not need any other include, then it is
self-contained.
--
js
suse labs
next prev parent reply other threads:[~2024-10-15 7:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 14:46 [PATCH] kfifo: don't include dma-mapping.h in kfifo.h Christoph Hellwig
2024-10-15 7:38 ` Jiri Slaby
2024-10-15 7:40 ` Christoph Hellwig
2024-10-15 7:53 ` Jiri Slaby [this message]
2024-10-15 7:56 ` Christoph Hellwig
2024-10-15 8:19 ` Jiri Slaby
2024-10-15 7:47 ` Jiri Slaby
2024-10-15 7:50 ` Christoph Hellwig
2024-10-15 7:55 ` Jiri Slaby
2024-10-15 7:57 ` Christoph Hellwig
2024-10-15 8:03 ` Jiri Slaby
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=7f723486-237f-47d2-b9c1-e5312876dfb5@kernel.org \
--to=jirislaby@kernel.org \
--cc=hch@lst.de \
--cc=jassisinghbrar@gmail.com \
--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 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.