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 0/5] crc16: Remove duplicate implementations
Date: Tue, 12 Apr 2022 11:20:39 +0200	[thread overview]
Message-ID: <20220412092044.25133-1-pali@kernel.org> (raw)

This patch series removes duplicate implementations of CRC-16 with
polynomial x^16 + x^15 + x^2 + 1. One implementation is enough.

Atsha 5/5 patch depends on another atsha patch:
https://patchwork.ozlabs.org/project/uboot/patch/20220402223634.20256-1-pali@kernel.org/

Pali Rohár (5):
  crc16-ccitt: Rename file with CRC-16-CCITT implementation to
    crc16-ccitt.c
  crc16: Rename fs/ubifs/crc16.h to include/linux/crc16.h
  crc16: Move standard CRC-16 implementation from ubifs to lib
  fs: ext4: Use CRC-16 implementation from linux/crc16.h
  misc: atsha204a: Remove duplicate CRC-16 implementation

 drivers/misc/Kconfig                |   1 +
 drivers/misc/atsha204a-i2c.c        | 122 +--------------------------
 fs/ext4/Makefile                    |   2 +-
 fs/ext4/crc16.c                     |  62 --------------
 fs/ext4/crc16.h                     |  16 ----
 fs/ext4/ext4_common.c               |   8 +-
 fs/ext4/ext4_common.h               |   2 +-
 fs/ubifs/Makefile                   |   2 +-
 fs/ubifs/crc16.c                    |  60 --------------
 fs/ubifs/lpt.c                      |   2 +-
 fs/ubifs/lpt_commit.c               |   2 +-
 {fs/ubifs => include/linux}/crc16.h |   0
 include/u-boot/crc.h                |   5 +-
 lib/Makefile                        |   7 +-
 lib/crc16-ccitt.c                   |  84 +++++++++++++++++++
 lib/crc16.c                         | 124 +++++++++++-----------------
 tools/Makefile                      |   2 +-
 17 files changed, 156 insertions(+), 345 deletions(-)
 delete mode 100644 fs/ext4/crc16.c
 delete mode 100644 fs/ext4/crc16.h
 delete mode 100644 fs/ubifs/crc16.c
 rename {fs/ubifs => include/linux}/crc16.h (100%)
 create mode 100644 lib/crc16-ccitt.c

-- 
2.20.1


             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 Pali Rohár [this message]
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 ` [PATCH 2/5] crc16: Rename fs/ubifs/crc16.h to include/linux/crc16.h Pali Rohár
2022-04-21 14:34   ` 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-1-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