* [PATCH] btrfs-progs: Fix bad kernel header non-flat include case
@ 2020-04-08 7:04 Qu Wenruo
2020-04-16 12:56 ` David Sterba
0 siblings, 1 reply; 2+ messages in thread
From: Qu Wenruo @ 2020-04-08 7:04 UTC (permalink / raw)
To: linux-btrfs
If we're compiling using system header, we should include
<btrfs/crc32c.h> other than "btrfs/crc32.h".
Fixes: 2efe160bc757 ("btrfs-progs: move name hashing functions to ctree.h and delete hash.h")
Signed-off-by: Qu Wenruo <wqu@suse.com>
---
ctree.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ctree.h b/ctree.h
index 9d69fa946079..df830956fdb8 100644
--- a/ctree.h
+++ b/ctree.h
@@ -38,7 +38,7 @@
#include <btrfs/extent_io.h>
#include <btrfs/ioctl.h>
#include <btrfs/sizes.h>
-#include "btrfs/crc32c.h"
+#include <btrfs/crc32c.h>
#endif /* BTRFS_FLAT_INCLUDES */
struct btrfs_root;
--
2.26.0
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] btrfs-progs: Fix bad kernel header non-flat include case
2020-04-08 7:04 [PATCH] btrfs-progs: Fix bad kernel header non-flat include case Qu Wenruo
@ 2020-04-16 12:56 ` David Sterba
0 siblings, 0 replies; 2+ messages in thread
From: David Sterba @ 2020-04-16 12:56 UTC (permalink / raw)
To: Qu Wenruo; +Cc: linux-btrfs
On Wed, Apr 08, 2020 at 03:04:12PM +0800, Qu Wenruo wrote:
> If we're compiling using system header, we should include
> <btrfs/crc32c.h> other than "btrfs/crc32.h".
>
> Fixes: 2efe160bc757 ("btrfs-progs: move name hashing functions to ctree.h and delete hash.h")
> Signed-off-by: Qu Wenruo <wqu@suse.com>
Added to devel, thanks.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-04-16 12:57 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-04-08 7:04 [PATCH] btrfs-progs: Fix bad kernel header non-flat include case Qu Wenruo
2020-04-16 12:56 ` David Sterba
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).