public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali@kernel.org>
To: "Simon Glass" <sjg@chromium.org>, "Bin Meng" <bmeng.cn@gmail.com>,
	"Adrian Fiergolski" <adrian.fiergolski@fastree3d.com>,
	"Marek Behún" <marek.behun@nic.cz>, "Stefan Roese" <sr@denx.de>
Cc: u-boot@lists.denx.de
Subject: [PATCH 2/5] crc16: Rename fs/ubifs/crc16.h to include/linux/crc16.h
Date: Tue, 12 Apr 2022 11:20:41 +0200	[thread overview]
Message-ID: <20220412092044.25133-3-pali@kernel.org> (raw)
In-Reply-To: <20220412092044.25133-1-pali@kernel.org>

File fs/ubifs/crc16.h is standard linux's crc16.h include file. So move it
from fs/ubifs to include/linux where are also other linux include files.

Signed-off-by: Pali Rohár <pali@kernel.org>
---
 fs/ubifs/crc16.c                    | 2 +-
 fs/ubifs/lpt.c                      | 2 +-
 fs/ubifs/lpt_commit.c               | 2 +-
 {fs/ubifs => include/linux}/crc16.h | 0
 4 files changed, 3 insertions(+), 3 deletions(-)
 rename {fs/ubifs => include/linux}/crc16.h (100%)

diff --git a/fs/ubifs/crc16.c b/fs/ubifs/crc16.c
index 443ccf855d5e..7cf33fc7eb61 100644
--- a/fs/ubifs/crc16.c
+++ b/fs/ubifs/crc16.c
@@ -6,7 +6,7 @@
  */
 
 #include <linux/types.h>
-#include "crc16.h"
+#include <linux/crc16.h>
 
 /** CRC table for the CRC-16. The poly is 0x8005 (x^16 + x^15 + x^2 + 1) */
 u16 const crc16_table[256] = {
diff --git a/fs/ubifs/lpt.c b/fs/ubifs/lpt.c
index 62748b0210b2..27835e60d2c0 100644
--- a/fs/ubifs/lpt.c
+++ b/fs/ubifs/lpt.c
@@ -42,7 +42,7 @@
 #include <linux/compat.h>
 #include <linux/err.h>
 #include <ubi_uboot.h>
-#include "crc16.h"
+#include <linux/crc16.h>
 #endif
 
 /**
diff --git a/fs/ubifs/lpt_commit.c b/fs/ubifs/lpt_commit.c
index 897d0014306c..ba0b19a1f2b2 100644
--- a/fs/ubifs/lpt_commit.c
+++ b/fs/ubifs/lpt_commit.c
@@ -23,7 +23,7 @@
 #include <linux/bitops.h>
 #include <linux/compat.h>
 #include <linux/err.h>
-#include "crc16.h"
+#include <linux/crc16.h>
 #endif
 #include "ubifs.h"
 
diff --git a/fs/ubifs/crc16.h b/include/linux/crc16.h
similarity index 100%
rename from fs/ubifs/crc16.h
rename to include/linux/crc16.h
-- 
2.20.1


  parent reply	other threads:[~2022-04-12  9:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-12  9:20 [PATCH 0/5] crc16: Remove duplicate implementations Pali Rohár
2022-04-12  9:20 ` [PATCH 1/5] crc16-ccitt: Rename file with CRC-16-CCITT implementation to crc16-ccitt.c Pali Rohár
2022-04-21 14:34   ` Stefan Roese
2022-04-21 23:56   ` Tom Rini
2022-04-12  9:20 ` Pali Rohár [this message]
2022-04-21 14:34   ` [PATCH 2/5] crc16: Rename fs/ubifs/crc16.h to include/linux/crc16.h Stefan Roese
2022-04-21 23:56   ` Tom Rini
2022-04-12  9:20 ` [PATCH 3/5] crc16: Move standard CRC-16 implementation from ubifs to lib Pali Rohár
2022-04-21 14:35   ` Stefan Roese
2022-04-21 23:57   ` Tom Rini
2022-04-12  9:20 ` [PATCH 4/5] fs: ext4: Use CRC-16 implementation from linux/crc16.h Pali Rohár
2022-04-21 14:35   ` Stefan Roese
2022-04-21 23:57   ` Tom Rini
2022-04-12  9:20 ` [PATCH 5/5] misc: atsha204a: Remove duplicate CRC-16 implementation Pali Rohár
2022-04-21 14:35   ` Stefan Roese
2022-04-21 23:57   ` Tom Rini

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=20220412092044.25133-3-pali@kernel.org \
    --to=pali@kernel.org \
    --cc=adrian.fiergolski@fastree3d.com \
    --cc=bmeng.cn@gmail.com \
    --cc=marek.behun@nic.cz \
    --cc=sjg@chromium.org \
    --cc=sr@denx.de \
    --cc=u-boot@lists.denx.de \
    /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