From: mchristi@redhat.com
To: linux-ext4@vger.kernel.org, linux-block@vger.kernel.org
Subject: [PATCH 0/2] linux-block for-next REQ_OP fixes
Date: Wed, 8 Jun 2016 15:49:39 -0500 [thread overview]
Message-ID: <1465418981-7360-1-git-send-email-mchristi@redhat.com> (raw)
Hi Jens,
The following patches fix 2 issues from the REQ_OP patch
merge.
They were made over your for-next branch.
next reply other threads:[~2016-06-08 20:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 20:49 mchristi [this message]
2016-06-08 20:49 ` [PATCH 1/2] ext4: use bio op helprs in ext4 crypto code mchristi
2016-06-08 21:00 ` Jens Axboe
2016-06-08 20:49 ` [PATCH 2/2] mg_disk: fix enum REQ_OP_ kbuild error mchristi
2016-06-08 21:00 ` [PATCH 0/2] linux-block for-next REQ_OP fixes 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=1465418981-7360-1-git-send-email-mchristi@redhat.com \
--to=mchristi@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-ext4@vger.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).