From: Thierry Reding <thierry.reding@gmail.com>
To: Dave Kleikamp <dave.kleikamp@oracle.com>, Jens Axboe <axboe@kernel.dk>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: manual merge of the block tree
Date: Fri, 25 Oct 2013 17:03:46 +0200 [thread overview]
Message-ID: <1382713426-2680-2-git-send-email-treding@nvidia.com> (raw)
In-Reply-To: <1382713426-2680-1-git-send-email-treding@nvidia.com>
Today's linux-next tree of the block tree got conflicts in
include/linux/blk_types.h
caused by commits 1063cee (nfs: simplify swap) and 8382f11 (block: make
rq->cmd_flags be 64-bit).
I fixed them up (see below). Please verify that the resolution looks good.
Thanks,
Thierry
---
diff --cc include/linux/blk_types.h
index 1bea25f,238ef0e..2c1c8c9
--- a/include/linux/blk_types.h
+++ b/include/linux/blk_types.h
@@@ -176,7 -176,9 +176,8 @@@ enum rq_flag_bits
__REQ_FLUSH_SEQ, /* request for flush sequence */
__REQ_IO_STAT, /* account I/O stat */
__REQ_MIXED_MERGE, /* merge of different types, fail separately */
- __REQ_KERNEL, /* direct IO to kernel pages */
__REQ_PM, /* runtime pm request */
+ __REQ_END, /* last of chain of requests */
__REQ_NR_BITS, /* stops here */
};
@@@ -205,27 -207,29 +206,28 @@@
#define REQ_NOMERGE_FLAGS \
(REQ_NOMERGE | REQ_STARTED | REQ_SOFTBARRIER | REQ_FLUSH | REQ_FUA)
- #define REQ_RAHEAD (1 << __REQ_RAHEAD)
- #define REQ_THROTTLED (1 << __REQ_THROTTLED)
-
- #define REQ_SORTED (1 << __REQ_SORTED)
- #define REQ_SOFTBARRIER (1 << __REQ_SOFTBARRIER)
- #define REQ_FUA (1 << __REQ_FUA)
- #define REQ_NOMERGE (1 << __REQ_NOMERGE)
- #define REQ_STARTED (1 << __REQ_STARTED)
- #define REQ_DONTPREP (1 << __REQ_DONTPREP)
- #define REQ_QUEUED (1 << __REQ_QUEUED)
- #define REQ_ELVPRIV (1 << __REQ_ELVPRIV)
- #define REQ_FAILED (1 << __REQ_FAILED)
- #define REQ_QUIET (1 << __REQ_QUIET)
- #define REQ_PREEMPT (1 << __REQ_PREEMPT)
- #define REQ_ALLOCED (1 << __REQ_ALLOCED)
- #define REQ_COPY_USER (1 << __REQ_COPY_USER)
- #define REQ_FLUSH (1 << __REQ_FLUSH)
- #define REQ_FLUSH_SEQ (1 << __REQ_FLUSH_SEQ)
- #define REQ_IO_STAT (1 << __REQ_IO_STAT)
- #define REQ_MIXED_MERGE (1 << __REQ_MIXED_MERGE)
- #define REQ_SECURE (1 << __REQ_SECURE)
- #define REQ_PM (1 << __REQ_PM)
+ #define REQ_RAHEAD (1ULL << __REQ_RAHEAD)
+ #define REQ_THROTTLED (1ULL << __REQ_THROTTLED)
+
+ #define REQ_SORTED (1ULL << __REQ_SORTED)
+ #define REQ_SOFTBARRIER (1ULL << __REQ_SOFTBARRIER)
+ #define REQ_FUA (1ULL << __REQ_FUA)
+ #define REQ_NOMERGE (1ULL << __REQ_NOMERGE)
+ #define REQ_STARTED (1ULL << __REQ_STARTED)
+ #define REQ_DONTPREP (1ULL << __REQ_DONTPREP)
+ #define REQ_QUEUED (1ULL << __REQ_QUEUED)
+ #define REQ_ELVPRIV (1ULL << __REQ_ELVPRIV)
+ #define REQ_FAILED (1ULL << __REQ_FAILED)
+ #define REQ_QUIET (1ULL << __REQ_QUIET)
+ #define REQ_PREEMPT (1ULL << __REQ_PREEMPT)
+ #define REQ_ALLOCED (1ULL << __REQ_ALLOCED)
+ #define REQ_COPY_USER (1ULL << __REQ_COPY_USER)
+ #define REQ_FLUSH (1ULL << __REQ_FLUSH)
+ #define REQ_FLUSH_SEQ (1ULL << __REQ_FLUSH_SEQ)
+ #define REQ_IO_STAT (1ULL << __REQ_IO_STAT)
+ #define REQ_MIXED_MERGE (1ULL << __REQ_MIXED_MERGE)
+ #define REQ_SECURE (1ULL << __REQ_SECURE)
-#define REQ_KERNEL (1ULL << __REQ_KERNEL)
+ #define REQ_PM (1ULL << __REQ_PM)
+ #define REQ_END (1ULL << __REQ_END)
#endif /* __LINUX_BLK_TYPES_H */
next prev parent reply other threads:[~2013-10-25 15:03 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 15:03 linux-next: Tree for Oct 25 Thierry Reding
2013-10-25 15:03 ` Thierry Reding [this message]
2013-10-25 19:46 ` linux-next: Tree for Oct 25 (powercap_sys.c) Randy Dunlap
2013-10-25 22:17 ` Srinivas Pandruvada
2013-10-25 22:30 ` Srinivas Pandruvada
2013-10-25 21:01 ` linux-next: Tree for Oct 25 Guenter Roeck
2013-10-25 21:12 ` linux-next: Tree for Oct 25 (of_gpio.h) Randy Dunlap
2013-10-25 22:31 ` linux-next: Tree for Oct 25 Randy Dunlap
2013-10-26 16:59 ` Mark Brown
2013-10-28 8:01 ` Thierry Reding
2013-10-28 16:53 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2013-10-14 14:48 linux-next: Tree for Oct 14 Thierry Reding
2013-10-14 14:48 ` linux-next: manual merge of the block tree Thierry Reding
2013-10-11 19:04 Mark Brown
2013-10-01 11:03 linux-next: Tree for Oct 1 Thierry Reding
2013-10-01 11:07 ` linux-next: manual merge of the block tree Thierry Reding
2013-09-30 11:26 linux-next: manual merge of the bcon tree Thierry Reding
2013-09-30 11:26 ` linux-next: manual merge of the block tree Thierry Reding
2008-12-15 7:08 Stephen Rothwell
2008-11-19 3:21 Stephen Rothwell
2008-11-19 9:14 ` Jens Axboe
2008-11-19 9:32 ` Stephen Rothwell
2008-11-07 6:14 Stephen Rothwell
2008-11-07 6:10 Stephen Rothwell
2008-11-07 9:50 ` Jens Axboe
2008-11-07 10:07 ` Stephen Rothwell
2008-10-15 7:40 Stephen Rothwell
2008-09-05 6:12 Stephen Rothwell
2008-09-05 6:22 ` Jens Axboe
2008-09-05 13:58 ` James Bottomley
2008-09-03 5:58 Stephen Rothwell
2008-09-03 5:55 Stephen Rothwell
2008-09-02 6:06 Stephen Rothwell
2008-09-02 5:59 Stephen Rothwell
2008-08-28 5:30 Stephen Rothwell
2008-08-27 5:48 Stephen Rothwell
2008-08-27 5:47 Stephen Rothwell
2008-06-27 6:13 Stephen Rothwell
2008-06-27 8:30 ` Ingo Molnar
2008-06-27 8:47 ` Jens Axboe
2008-06-27 9:26 ` Ingo Molnar
2008-06-27 9:57 ` Ingo Molnar
2008-06-27 10:11 ` Ingo Molnar
2008-06-27 11:21 ` Jens Axboe
2008-06-27 11:21 ` Jens Axboe
2008-06-27 11:18 ` Jens Axboe
2008-06-27 6:09 Stephen Rothwell
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=1382713426-2680-2-git-send-email-treding@nvidia.com \
--to=thierry.reding@gmail.com \
--cc=axboe@kernel.dk \
--cc=dave.kleikamp@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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).