linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Martin Wilck <mwilck@suse.com>
Cc: Jens Axboe <axboe@kernel.dk>, Tejun Heo <tj@kernel.org>,
	Hannes Reinecke <hare@suse.de>,
	James Bottomley <jejb@linux.vnet.ibm.com>,
	Christoph Hellwig <hch@lst.de>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Bart Van Assche <Bart.VanAssche@sandisk.com>,
	linux-block@vger.kernel.org, linux-ide@vger.kernel.org,
	linux-scsi@vger.kernel.org
Subject: Re: Reminder: [PATCH v2 0/5] block: skip media change event handling if unsupported
Date: Tue, 19 Mar 2019 14:21:03 -0400	[thread overview]
Message-ID: <yq1ftriene8.fsf@oracle.com> (raw)
In-Reply-To: <b4971cf31e301dd32a37c914090ce574823fcd06.camel@suse.com> (Martin Wilck's message of "Fri, 15 Mar 2019 15:25:26 +0100")


Martin,

> Gentle review reminder.

Please resubmit.

-- 
Martin K. Petersen	Oracle Linux Engineering

      reply	other threads:[~2019-03-19 18:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-05 11:37 [PATCH v2 0/5] block: skip media change event handling if unsupported Martin Wilck
2019-02-05 11:37 ` [PATCH v2 1/5] block: genhd: remove async_events field Martin Wilck
2019-02-05 11:37 ` [PATCH v2 2/5] block: disk_events: introduce event flags Martin Wilck
2019-02-05 11:37 ` [PATCH v2 3/5] Revert "ide: unexport DISK_EVENT_MEDIA_CHANGE for ide-gd and ide-cd" Martin Wilck
2019-02-05 11:37 ` [PATCH v2 4/5] Revert "block: unexport DISK_EVENT_MEDIA_CHANGE for legacy/fringe drivers" Martin Wilck
2019-02-05 11:37 ` [PATCH v2 5/5] block: check_events: don't bother with events if unsupported Martin Wilck
2019-03-15 14:25 ` Reminder: [PATCH v2 0/5] block: skip media change event handling " Martin Wilck
2019-03-19 18:21   ` Martin K. Petersen [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=yq1ftriene8.fsf@oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=Bart.VanAssche@sandisk.com \
    --cc=axboe@kernel.dk \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mwilck@suse.com \
    --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).