From: Hannes Reinecke <hare@suse.de>
To: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>
Cc: Tejun Heo <tj@kernel.org>, linux-block@vger.kernel.org
Subject: Re: [PATCH 1/2] block: move the disk events code to a separate file
Date: Thu, 24 Jun 2021 09:53:00 +0200 [thread overview]
Message-ID: <23b45c88-a968-9c8e-d111-22aea6e81827@suse.de> (raw)
In-Reply-To: <20210624073843.251178-2-hch@lst.de>
On 6/24/21 9:38 AM, Christoph Hellwig wrote:
> Move the code for handling disk events from genhd.c into a new file
> as it isn't very related to the rest of the file while at the same
> time requiring lots of forward declarations.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> block/Makefile | 3 +-
> block/blk.h | 5 +
> block/disk-events.c | 484 +++++++++++++++++++++++++++++++++++++++++++
> block/genhd.c | 492 --------------------------------------------
> 4 files changed, 491 insertions(+), 493 deletions(-)
> create mode 100644 block/disk-events.c
>
Reviewed-by: Hannes Reinecke <hare@suse.de>
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), GF: Felix Imendörffer
next prev parent reply other threads:[~2021-06-24 7:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-24 7:38 disk events cleanup Christoph Hellwig
2021-06-24 7:38 ` [PATCH 1/2] block: move the disk events code to a separate file Christoph Hellwig
2021-06-24 7:53 ` Hannes Reinecke [this message]
2021-06-24 7:38 ` [PATCH 2/2] block: add the events* attributes to disk_attrs Christoph Hellwig
2021-06-24 7:53 ` Hannes Reinecke
2021-06-24 18:00 ` disk events cleanup 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=23b45c88-a968-9c8e-d111-22aea6e81827@suse.de \
--to=hare@suse.de \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=tj@kernel.org \
/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).