Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: "Christoph Böhmwalder" <christoph.boehmwalder@linbit.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Philipp Reisner <philipp.reisner@linbit.com>,
	linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
	Lars Ellenberg <lars.ellenberg@linbit.com>,
	drbd-dev@lists.linbit.com
Subject: [Drbd-dev] [PATCH 0/4] lru_cache improvements, DRBD license identifiers
Date: Tue, 22 Nov 2022 14:42:57 +0100	[thread overview]
Message-ID: <20221122134301.69258-1-christoph.boehmwalder@linbit.com> (raw)

Here are some improvements to the lru_cache; mostly just cleanups that
we missed to send upstream over the years.

The last patch makes the SPDX license headers in DRBD consistent so
that they all represent GPL 2.0.

Christoph Böhmwalder (2):
  lru_cache: remove compiled out code
  drbd: use consistent license

Joel Colledge (1):
  lru_cache: remove unused lc_private, lc_set, lc_index_of

Lars Ellenberg (1):
  lru_cache: use atomic operations when accessing lc->flags, always

 drivers/block/drbd/Kconfig             |  2 +-
 drivers/block/drbd/Makefile            |  2 +-
 drivers/block/drbd/drbd_actlog.c       |  2 +-
 drivers/block/drbd/drbd_bitmap.c       |  2 +-
 drivers/block/drbd/drbd_debugfs.c      |  2 +-
 drivers/block/drbd/drbd_debugfs.h      |  2 +-
 drivers/block/drbd/drbd_int.h          |  2 +-
 drivers/block/drbd/drbd_interval.c     |  2 +-
 drivers/block/drbd/drbd_interval.h     |  2 +-
 drivers/block/drbd/drbd_main.c         |  2 +-
 drivers/block/drbd/drbd_nl.c           |  2 +-
 drivers/block/drbd/drbd_nla.c          |  2 +-
 drivers/block/drbd/drbd_nla.h          |  2 +-
 drivers/block/drbd/drbd_proc.c         |  2 +-
 drivers/block/drbd/drbd_protocol.h     |  2 +-
 drivers/block/drbd/drbd_receiver.c     |  2 +-
 drivers/block/drbd/drbd_req.c          |  2 +-
 drivers/block/drbd/drbd_req.h          |  2 +-
 drivers/block/drbd/drbd_state.c        |  2 +-
 drivers/block/drbd/drbd_state.h        |  2 +-
 drivers/block/drbd/drbd_state_change.h |  2 +-
 drivers/block/drbd/drbd_strings.c      |  2 +-
 drivers/block/drbd/drbd_strings.h      |  2 +-
 drivers/block/drbd/drbd_vli.h          |  2 +-
 drivers/block/drbd/drbd_worker.c       |  2 +-
 include/linux/lru_cache.h              |  3 --
 lib/lru_cache.c                        | 59 +-------------------------
 27 files changed, 27 insertions(+), 85 deletions(-)

-- 
2.38.1


             reply	other threads:[~2022-11-22 13:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-22 13:42 Christoph Böhmwalder [this message]
2022-11-22 13:42 ` [Drbd-dev] [PATCH 1/4] lru_cache: use atomic operations when accessing lc->flags, always Christoph Böhmwalder
2022-11-22 13:42 ` [Drbd-dev] [PATCH 2/4] lru_cache: remove compiled out code Christoph Böhmwalder
2022-11-22 13:43 ` [Drbd-dev] [PATCH 3/4] lru_cache: remove unused lc_private, lc_set, lc_index_of Christoph Böhmwalder
2022-11-22 13:43 ` [Drbd-dev] [PATCH 4/4] drbd: use consistent license Christoph Böhmwalder
2022-11-23  2:39 ` [Drbd-dev] [PATCH 0/4] lru_cache improvements, DRBD license identifiers Jens Axboe

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=20221122134301.69258-1-christoph.boehmwalder@linbit.com \
    --to=christoph.boehmwalder@linbit.com \
    --cc=axboe@kernel.dk \
    --cc=drbd-dev@lists.linbit.com \
    --cc=lars.ellenberg@linbit.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=philipp.reisner@linbit.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