s390/eadm: fix CONFIG_BLOCK include dependency

"Linux Kernel Mailing List" <[email protected]>
Newsgroups gmane.linux.kernel.commits.head
Message-ID <[email protected]>
Web:        https://git.kernel.org/torvalds/c/366b77ae43c5a3bf1a367f15ec8bc16e05035f14
Commit:     366b77ae43c5a3bf1a367f15ec8bc16e05035f14
Parent:     4bf772b14675411a69b3c807f73006de0fe4b649
Refname:    refs/heads/master
Author:     Sebastian Ott <[email protected]>
AuthorDate: Tue Jan 23 13:58:05 2018 +0100
Committer:  Martin Schwidefsky <[email protected]>
CommitDate: Fri Feb 2 10:47:14 2018 +0100

    s390/eadm: fix CONFIG_BLOCK include dependency
    
    Commit 2a842acab109 ("block: introduce new block status code type")
    added blk_status_t usage to the eadm subchannel driver. However
    blk_status_t is unknown when included via <linux/blkdev.h> for CONFIG_BLOCK=n.
    
    Only include <linux/blk_types.h> since this is the only dependency eadm has.
    
    This fixes build failures like below:
    In file included from drivers/s390/cio/eadm_sch.c:24:0:
    ./arch/s390/include/asm/eadm.h:111:4: error: unknown type name 'blk_status_t'; did you mean 'si_status'?
        blk_status_t error);
    
    Reported-by: Heiko Carstens <[email protected]>
    Signed-off-by: Sebastian Ott <[email protected]>
    Signed-off-by: Martin Schwidefsky <[email protected]>
---
 arch/s390/include/asm/eadm.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/s390/include/asm/eadm.h b/arch/s390/include/asm/eadm.h
index eb5323161f11..bb63b2afdf6f 100644
--- a/arch/s390/include/asm/eadm.h
+++ b/arch/s390/include/asm/eadm.h
@@ -4,7 +4,7 @@
 
 #include <linux/types.h>
 #include <linux/device.h>
-#include <linux/blkdev.h>
+#include <linux/blk_types.h>
 
 struct arqb {
 	u64 data;
--
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.