From: Jens Axboe <axboe@kernel.dk>
To: "Christoph Böhmwalder" <christoph.boehmwalder@linbit.com>
Cc: drbd-dev@lists.linbit.com, linux-kernel@vger.kernel.org,
Lars Ellenberg <lars.ellenberg@linbit.com>,
Philipp Reisner <philipp.reisner@linbit.com>,
linux-block@vger.kernel.org
Subject: Re: [RESEND PATCH 0/3] DRBD file structure reorganization
Date: Fri, 13 Jan 2023 08:43:28 -0700 [thread overview]
Message-ID: <167362460873.11790.14664102108857579461.b4-ty@kernel.dk> (raw)
In-Reply-To: <20230113123506.144082-1-christoph.boehmwalder@linbit.com>
On Fri, 13 Jan 2023 13:35:03 +0100, Christoph Böhmwalder wrote:
> To make our lives easier when sending future, more complex patches,
> we want to align the file structure as best as possible with what we
> have in the out-of-tree module.
>
> Christoph Böhmwalder (3):
> drbd: split off drbd_buildtag into separate file
> drbd: drop API_VERSION define
> drbd: split off drbd_config into separate file
>
> [...]
Applied, thanks!
[1/3] drbd: split off drbd_buildtag into separate file
commit: c058c9c9dcb137f395e1946b0f3595538479b3fd
[2/3] drbd: drop API_VERSION define
commit: a68176e0f7cf1b68a84c3b7c08271af0d3d2e796
[3/3] drbd: split off drbd_config into separate file
commit: 26547cb41a9f459535300275a319681a70cf69fe
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2023-01-13 15:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 12:35 [RESEND PATCH 0/3] DRBD file structure reorganization Christoph Böhmwalder
2023-01-13 12:35 ` [PATCH 1/3] drbd: split off drbd_buildtag into separate file Christoph Böhmwalder
2023-01-13 12:35 ` [PATCH 2/3] drbd: drop API_VERSION define Christoph Böhmwalder
2023-01-13 12:35 ` [PATCH 3/3] drbd: split off drbd_config into separate file Christoph Böhmwalder
2023-01-13 15:43 ` 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=167362460873.11790.14664102108857579461.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;
as well as URLs for NNTP newsgroup(s).