All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@intel.com>
To: Namhyung Kim <namhyung@gmail.com>
Cc: Jens Axboe <jaxboe@fusionio.com>,
	linux-kernel@vger.kernel.org, gregkh@suse.de
Subject: Re: [PATCH reRESEND] block: add REQ_SECURE to REQ_COMMON_MASK
Date: Mon, 20 Jun 2011 10:41:42 +0300	[thread overview]
Message-ID: <4DFEF9B6.7000402@intel.com> (raw)
In-Reply-To: <1308280320-3510-1-git-send-email-namhyung@gmail.com>

On 17/06/11 06:12, Namhyung Kim wrote:
> Add REQ_SECURE flag to REQ_COMMON_MASK so that
> init_request_from_bio() can pass it to @req->cmd_flags.
>
> Signed-off-by: Namhyung Kim<namhyung@gmail.com>
> ---
> Send it again due to Adrian's mail delivery failure.
>
>   include/linux/blk_types.h |    2 +-
>   1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/include/linux/blk_types.h b/include/linux/blk_types.h
> index 2a7cea53ca0d..6395692b2e7a 100644
> --- a/include/linux/blk_types.h
> +++ b/include/linux/blk_types.h
> @@ -167,7 +167,7 @@ enum rq_flag_bits {
>   	(REQ_FAILFAST_DEV | REQ_FAILFAST_TRANSPORT | REQ_FAILFAST_DRIVER)
>   #define REQ_COMMON_MASK \
>   	(REQ_WRITE | REQ_FAILFAST_MASK | REQ_SYNC | REQ_META | REQ_DISCARD | \
> -	 REQ_NOIDLE | REQ_FLUSH | REQ_FUA)
> +	 REQ_NOIDLE | REQ_FLUSH | REQ_FUA | REQ_SECURE)
>   #define REQ_CLONE_MASK		REQ_COMMON_MASK
>
>   #define REQ_RAHEAD		(1<<  __REQ_RAHEAD)

Acked-by: Adrian Hunter <adrian.hunter@intel.com>

The fix needs to go back to 2.6.36

  reply	other threads:[~2011-06-20  7:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-17  2:43 [PATCH RESEND] block: add REQ_SECURE to REQ_COMMON_MASK Namhyung Kim
2011-06-17  3:12 ` [PATCH reRESEND] " Namhyung Kim
2011-06-20  7:41   ` Adrian Hunter [this message]
2011-06-20 11:23   ` 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=4DFEF9B6.7000402@intel.com \
    --to=adrian.hunter@intel.com \
    --cc=gregkh@suse.de \
    --cc=jaxboe@fusionio.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@gmail.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 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.