From: David Sterba <dsterba@suse.cz>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Qu Wenruo <quwenruo.btrfs@gmx.com>,
linux-kernel@vger.kernel.org, Chris Mason <clm@fb.com>,
Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: don't include '<linux/rwlock_types.h>' directly
Date: Mon, 23 Dec 2024 20:18:52 +0100 [thread overview]
Message-ID: <20241223191852.GJ31418@twin.jikos.cz> (raw)
In-Reply-To: <Z2QDK9uFrXUIhJn2@shikoro>
On Thu, Dec 19, 2024 at 12:27:39PM +0100, Wolfram Sang wrote:
> Hi,
>
> > > -#include <linux/rwlock_types.h>
> > > +#include <linux/spinlock_types.h>
> >
> > I think we can just remove the *_type.h include header completely.
>
> I agree, spinlock.h is enough.
I've updated the fix to drop rwlock_types.h as spinlock.h is already
there. Added to for-next, thanks.
prev parent reply other threads:[~2024-12-23 19:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 7:05 [PATCH] btrfs: don't include '<linux/rwlock_types.h>' directly Wolfram Sang
2024-12-17 7:14 ` Qu Wenruo
2024-12-19 11:27 ` Wolfram Sang
2024-12-23 19:18 ` David Sterba [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=20241223191852.GJ31418@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=wsa+renesas@sang-engineering.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox