From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>
Cc: Tejun Heo <tj@kernel.org>, linux-block@vger.kernel.org
Subject: Re: disk events cleanup
Date: Thu, 24 Jun 2021 12:00:40 -0600 [thread overview]
Message-ID: <12615047-efe6-09df-9a93-441f918c28b1@kernel.dk> (raw)
In-Reply-To: <20210624073843.251178-1-hch@lst.de>
On 6/24/21 1:38 AM, Christoph Hellwig wrote:
> Hi all,
>
> this series first moves the disk events code into its own file, as it
> clearly is pretty distinct from the main genhd.c code (Tejun, feel free
> to add a Copyright statement as there was none), and then switch the
> registeration of the disk event attributes away from sysfs_create_files
> in favor of just adding them to the main disk class.
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2021-06-24 18:00 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
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 ` 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=12615047-efe6-09df-9a93-441f918c28b1@kernel.dk \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.