Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Christoph Böhmwalder <christoph.boehmwalder@linbit.com>
Cc: linux-block@vger.kernel.org,
	Lars Ellenberg <lars.ellenberg@linbit.com>,
	drbd-dev@lists.linbit.com, linux-kernel@vger.kernel.org,
	Philipp Reisner <philipp.reisner@linbit.com>
Subject: Re: [Drbd-dev] [PATCH 0/5] Backported DRBD printk/debug improvements
Date: Thu, 01 Dec 2022 11:49:06 -0700	[thread overview]
Message-ID: <166992054601.851878.10906244874618547606.b4-ty@kernel.dk> (raw)
In-Reply-To: <20221201110349.1282687-1-christoph.boehmwalder@linbit.com>

On Thu, 01 Dec 2022 12:03:45 +0100, Christoph Böhmwalder wrote:
> Some changes to DRBD's logging infrastructure, backported from the
> out-of-tree module.
> 
> Since the two code bases have diverged so much, it is tough to preserve
> authorship information without "putting words into someone's mouth". So
> I ended up using Originally-from tags to try and encode the original
> authors of these patches.
> 
> [...]

Applied, thanks!

[1/5] drbd: unify how failed assertions are logged
      commit: c3f8974198b41965c8f62099ba97f1293561cab2
[2/5] drbd: split polymorph printk to its own file
      commit: 136160c1732e3f86afd70c19ec6d1f5e6f79a7e9
[3/5] drbd: introduce dynamic debug
      commit: aa034695971124f673d4ccdd39cd7f269904ea86
[4/5] drbd: introduce drbd_ratelimit()
      commit: e3fa02d7d420c7cfb7077cc6eeb62c886ba5ff39
[5/5] drbd: add context parameter to expect() macro
      commit: 677b367275f8729546aee918e547056a90dbdc07

Best regards,
-- 
Jens Axboe



      parent reply	other threads:[~2022-12-01 18:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-01 11:03 [Drbd-dev] [PATCH 0/5] Backported DRBD printk/debug improvements Christoph Böhmwalder
2022-12-01 11:03 ` [Drbd-dev] [PATCH 1/5] drbd: unify how failed assertions are logged Christoph Böhmwalder
2022-12-01 11:03 ` [Drbd-dev] [PATCH 2/5] drbd: split polymorph printk to its own file Christoph Böhmwalder
2022-12-01 11:03 ` [Drbd-dev] [PATCH 3/5] drbd: introduce dynamic debug Christoph Böhmwalder
2022-12-01 11:03 ` [Drbd-dev] [PATCH 4/5] drbd: introduce drbd_ratelimit() Christoph Böhmwalder
2022-12-01 11:03 ` [Drbd-dev] [PATCH 5/5] drbd: add context parameter to expect() macro Christoph Böhmwalder
2022-12-01 18:49 ` Jens Axboe [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=166992054601.851878.10906244874618547606.b4-ty@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=christoph.boehmwalder@linbit.com \
    --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