1. 29 8月, 2019 2 次提交
  2. 28 8月, 2019 16 次提交
  3. 25 8月, 2019 7 次提交
  4. 24 8月, 2019 1 次提交
    • G
      erofs: move erofs out of staging · 47e4937a
      Gao Xiang 提交于
      EROFS filesystem has been merged into linux-staging for a year.
      
      EROFS is designed to be a better solution of saving extra storage
      space with guaranteed end-to-end performance for read-only files
      with the help of reduced metadata, fixed-sized output compression
      and decompression inplace technologies.
      
      In the past year, EROFS was greatly improved by many people as
      a staging driver, self-tested, betaed by a large number of our
      internal users, successfully applied to almost all in-service
      HUAWEI smartphones as the part of EMUI 9.1 and proven to be stable
      enough to be moved out of staging.
      
      EROFS is a self-contained filesystem driver. Although there are
      still some TODOs to be more generic, we have a dedicated team
      actively keeping on working on EROFS in order to make it better
      with the evolution of Linux kernel as the other in-kernel filesystems.
      
      As Pavel suggested, it's better to do as one commit since git
      can do moves and all histories will be saved in this way.
      
      Let's promote it from staging and enhance it more actively as
      a "real" part of kernel for more wider scenarios!
      
      Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
      Cc: Alexander Viro <viro@zeniv.linux.org.uk>
      Cc: Andrew Morton <akpm@linux-foundation.org>
      Cc: Stephen Rothwell <sfr@canb.auug.org.au>
      Cc: Theodore Ts'o <tytso@mit.edu>
      Cc: Pavel Machek <pavel@denx.de>
      Cc: David Sterba <dsterba@suse.cz>
      Cc: Amir Goldstein <amir73il@gmail.com>
      Cc: Christoph Hellwig <hch@infradead.org>
      Cc: Darrick J . Wong <darrick.wong@oracle.com>
      Cc: Dave Chinner <david@fromorbit.com>
      Cc: Jaegeuk Kim <jaegeuk@kernel.org>
      Cc: Jan Kara <jack@suse.cz>
      Cc: Richard Weinberger <richard@nod.at>
      Cc: Linus Torvalds <torvalds@linux-foundation.org>
      Cc: Chao Yu <yuchao0@huawei.com>
      Cc: Miao Xie <miaoxie@huawei.com>
      Cc: Li Guifu <bluce.liguifu@huawei.com>
      Cc: Fang Wei <fangwei1@huawei.com>
      Signed-off-by: NGao Xiang <gaoxiang25@huawei.com>
      Link: https://lore.kernel.org/r/20190822213659.5501-1-hsiangkao@aol.comSigned-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      47e4937a
  5. 22 8月, 2019 7 次提交
  6. 21 8月, 2019 7 次提交
    • C
      staging: rts5208: remove redundant assignment to retval · 8467c3b4
      Colin Ian King 提交于
      Variable retval is initialized to a value that is never read and it
      is re-assigned later. The initialization is redundant and can be
      removed.
      
      Addresses-Coverity: ("Unused value")
      Signed-off-by: NColin Ian King <colin.king@canonical.com>
      Link: https://lore.kernel.org/r/20190818184649.13828-1-colin.king@canonical.comSigned-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      8467c3b4
    • E
      staging: kpc2000: kpc2000_i2c: Fix different address spaces warnings · 1327d35a
      Eduardo Barretto 提交于
      This patch fixes the following sparse warnings:
      
      kpc2000_i2c.c:137: warning: incorrect type in argument 1
                                         (different address spaces)
      kpc2000_i2c.c:137:    expected void const volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:137:    got void *
      kpc2000_i2c.c:146: warning: incorrect type in argument 2
                                         (different address spaces)
      kpc2000_i2c.c:146:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:146:    got void *
      kpc2000_i2c.c:147: warning: incorrect type in argument 1
                                         (different address spaces)
      kpc2000_i2c.c:147:    expected void const volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:147:    got void *
      kpc2000_i2c.c:166: warning: incorrect type in argument 1
                                         (different address spaces)
      kpc2000_i2c.c:166:    expected void const volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:166:    got void *
      kpc2000_i2c.c:166: warning: incorrect type in argument 2
                                        (different address spaces)
      kpc2000_i2c.c:166:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:166:    got void *
      kpc2000_i2c.c:168: warning: incorrect type in argument 1
                                         (different address spaces)
      kpc2000_i2c.c:168:    expected void const volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:168:    got void *
      kpc2000_i2c.c:168: warning: incorrect type in argument 2
                                         (different address spaces)
      kpc2000_i2c.c:168:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:168:    got void *
      kpc2000_i2c.c:171: warning: incorrect type in argument 1
                                         (different address spaces)
      kpc2000_i2c.c:171:    expected void const volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:171:    got void *
      kpc2000_i2c.c:174: warning: incorrect type in argument 2
                                         (different address spaces)
      kpc2000_i2c.c:174:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:174:    got void *
      kpc2000_i2c.c:193: warning: incorrect type in argument 2
                                         (different address spaces)
      kpc2000_i2c.c:193:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:193:    got void *
      kpc2000_i2c.c:194: warning: incorrect type in argument 1
                                         (different address spaces)
      kpc2000_i2c.c:194:    expected void const volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:194:    got void *
      kpc2000_i2c.c:214: warning: incorrect type in argument 2
                                        (different address spaces)
      kpc2000_i2c.c:214:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:214:    got void *
      kpc2000_i2c.c:219: warning: incorrect type in argument 1
                                        (different address spaces)
      kpc2000_i2c.c:219:    expected void const volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:219:    got void *
      kpc2000_i2c.c:226: warning: incorrect type in argument 2
                                        (different address spaces)
      kpc2000_i2c.c:226:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:226:    got void *
      kpc2000_i2c.c:238: warning: incorrect type in argument 1
                                         (different address spaces)
      kpc2000_i2c.c:238:    expected void const volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:238:    got void *
      kpc2000_i2c.c:244: warning: incorrect type in argument 2
                                        (different address spaces)
      kpc2000_i2c.c:244:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:244:    got void *
      kpc2000_i2c.c:252: warning: incorrect type in argument 1
                                        (different address spaces)
      kpc2000_i2c.c:252:    expected void const volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:252:    got void *
      kpc2000_i2c.c:257: warning: incorrect type in argument 2
                                        (different address spaces)
      kpc2000_i2c.c:257:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:257:    got void *
      kpc2000_i2c.c:259: warning: incorrect type in argument 2
      				   (different address spaces)
      kpc2000_i2c.c:259:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:259:    got void *
      kpc2000_i2c.c:267: warning: incorrect type in argument 1
                                         (different address spaces)
      kpc2000_i2c.c:267:    expected void const volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:267:    got void *
      kpc2000_i2c.c:273: warning: incorrect type in argument 1
                                         (different address spaces)
      kpc2000_i2c.c:273:    expected void const volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:273:    got void *
      kpc2000_i2c.c:293: warning: incorrect type in argument 2
                                         (different address spaces)
      kpc2000_i2c.c:293:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:293:    got void *
      kpc2000_i2c.c:294: warning: incorrect type in argument 2
                                         (different address spaces)
      kpc2000_i2c.c:294:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:294:    got void *
      kpc2000_i2c.c:309: warning: incorrect type in argument 2
                                         (different address spaces)
      kpc2000_i2c.c:309:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:309:    got void *
      kpc2000_i2c.c:312: warning: incorrect type in argument 2
                                         (different address spaces)
      kpc2000_i2c.c:312:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:312:    got void *
      kpc2000_i2c.c:317: warning: incorrect type in argument 1
                                         (different address spaces)
      kpc2000_i2c.c:317:    expected void const volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:317:    got void *
      kpc2000_i2c.c:324: warning: incorrect type in argument 1
                                         (different address spaces)
      kpc2000_i2c.c:324:    expected void const volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:324:    got void *
      kpc2000_i2c.c:328: warning: incorrect type in argument 1
                                         (different address spaces)
      kpc2000_i2c.c:328:    expected void const volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:328:    got void *
      kpc2000_i2c.c:329: warning: incorrect type in argument 2
                                         (different address spaces)
      kpc2000_i2c.c:329:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:329:    got void *
      kpc2000_i2c.c:330: warning: incorrect type in argument 2
                                         (different address spaces)
      kpc2000_i2c.c:330:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:330:    got void *
      kpc2000_i2c.c:338: warning: incorrect type in argument 1
                                         (different address spaces)
      kpc2000_i2c.c:338:    expected void const volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:338:    got void *
      kpc2000_i2c.c:340: warning: incorrect type in argument 2
                                         (different address spaces)
      kpc2000_i2c.c:340:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:340:    got void *
      kpc2000_i2c.c:342: warning: incorrect type in argument 2
                                         (different address spaces)
      kpc2000_i2c.c:342:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:342:    got void *
      kpc2000_i2c.c:350: warning: incorrect type in argument 1
                                        (different address spaces)
      kpc2000_i2c.c:350:    expected void const volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:350:    got void *
      kpc2000_i2c.c:350: warning: incorrect type in argument 2
                                        (different address spaces)
      kpc2000_i2c.c:350:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:350:    got void *
      kpc2000_i2c.c:351: warning: incorrect type in argument 1
                                         (different address spaces)
      kpc2000_i2c.c:351:    expected void const volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:351:    got void *
      kpc2000_i2c.c:414: warning: incorrect type in argument 2
                                         (different address spaces)
      kpc2000_i2c.c:414:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:414:    got void *
      kpc2000_i2c.c:420: warning: incorrect type in argument 2
                                         (different address spaces)
      kpc2000_i2c.c:420:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:420:    got void *
      kpc2000_i2c.c:422: warning: incorrect type in argument 2
                                         (different address spaces)
      kpc2000_i2c.c:422:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:422:    got void *
      kpc2000_i2c.c:427: warning: incorrect type in argument 2
                                         (different address spaces)
      kpc2000_i2c.c:427:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:427:    got void *
      kpc2000_i2c.c:428: warning: incorrect type in argument 2
                                         (different address spaces)
      kpc2000_i2c.c:428:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:428:    got void *
      kpc2000_i2c.c:430: warning: incorrect type in argument 2
                                         (different address spaces)
      kpc2000_i2c.c:430:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:430:    got void *
      kpc2000_i2c.c:435: warning: incorrect type in argument 2
                                         (different address spaces)
      kpc2000_i2c.c:435:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:435:    got void *
      kpc2000_i2c.c:436: warning: incorrect type in argument 2
                                         (different address spaces)
      kpc2000_i2c.c:436:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:436:    got void *
      kpc2000_i2c.c:438: warning: incorrect type in argument 2
                                         (different address spaces)
      kpc2000_i2c.c:438:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:438:    got void *
      kpc2000_i2c.c:439: warning: incorrect type in argument 2
                                         (different address spaces)
      kpc2000_i2c.c:439:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:439:    got void *
      kpc2000_i2c.c:445: warning: incorrect type in argument 2
                                         (different address spaces)
      kpc2000_i2c.c:445:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:445:    got void *
      kpc2000_i2c.c:446: warning: incorrect type in argument 2
                                         (different address spaces)
      kpc2000_i2c.c:446:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:446:    got void *
      kpc2000_i2c.c:454: warning: incorrect type in argument 2
                                         (different address spaces)
      kpc2000_i2c.c:454:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:454:    got void *
      kpc2000_i2c.c:459: warning: incorrect type in argument 2
                                         (different address spaces)
      kpc2000_i2c.c:459:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:459:    got void *
      kpc2000_i2c.c:461: warning: incorrect type in argument 2
                                         (different address spaces)
      kpc2000_i2c.c:461:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:461:    got void *
      kpc2000_i2c.c:472: warning: incorrect type in argument 1
                                         (different address spaces)
      kpc2000_i2c.c:472:    expected void const volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:472:    got void *
      kpc2000_i2c.c:472: warning: incorrect type in argument 2
                                         (different address spaces)
      kpc2000_i2c.c:472:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:472:    got void *
      kpc2000_i2c.c:475: warning: incorrect type in argument 1
                                         (different address spaces)
      kpc2000_i2c.c:475:    expected void const volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:475:    got void *
      kpc2000_i2c.c:475: warning: incorrect type in argument 2
                                         (different address spaces)
      kpc2000_i2c.c:475:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:475:    got void *
      kpc2000_i2c.c:493: warning: incorrect type in argument 1
                                         (different address spaces)
      kpc2000_i2c.c:493:    expected void const volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:493:    got void *
      kpc2000_i2c.c:493: warning: incorrect type in argument 2
                                         (different address spaces)
      kpc2000_i2c.c:493:    expected void volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:493:    got void *
      kpc2000_i2c.c:512: warning: incorrect type in argument 1
                                         (different address spaces)
      kpc2000_i2c.c:512:    expected void const volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:512:    got void *
      kpc2000_i2c.c:516: warning: incorrect type in argument 1
                                         (different address spaces)
      kpc2000_i2c.c:516:    expected void const volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:516:    got void *
      kpc2000_i2c.c:516: warning: incorrect type in argument 1
                                         (different address spaces)
      kpc2000_i2c.c:516:    expected void const volatile [noderef] <asn:2> *addr
      kpc2000_i2c.c:516:    got void *
      Signed-off-by: NEduardo Barretto <edusbarretto@gmail.com>
      Link: https://lore.kernel.org/r/20190818183555.7167-1-edusbarretto@gmail.comSigned-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      1327d35a
    • D
      staging: android: Remove ion device tree bindings from the TODO · be237202
      Donald Yandt 提交于
      Commit 23a4388f ("staging: android: ion: Remove file ion_chunk_heap.c")
      and eadbf7a3 ("staging: android: ion: Remove file ion_carveout_heap.c")
      removed the chunk and carveout heaps from ion but left behind the device
      tree bindings for them in the TODO, this patch removes it.
      Signed-off-by: NDonald Yandt <donald.yandt@gmail.com>
      Link: https://lore.kernel.org/r/20190818152023.891-1-donald.yandt@gmail.comSigned-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      be237202
    • C
      staging: rtl8712: Improve naming of include hearder guards · f55ef00e
      Christophe JAILLET 提交于
      Choose a better name for the include hearder guard used in rtl871x_io.h.
      '_IO_H_' is to generic and does not match the comment after the #endif.
      Use '_RTL871X_IO_H_' instead.
      
      Also make the comments in the #endif /* XXX */ match the name used in
      #ifndef.
      Signed-off-by: NChristophe JAILLET <christophe.jaillet@wanadoo.fr>
      Link: https://lore.kernel.org/r/20190818150609.3376-1-christophe.jaillet@wanadoo.frSigned-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      f55ef00e
    • G
      staging: erofs: avoid loop in submit chains · bfc4ccb1
      Gao Xiang 提交于
      As reported by erofs-utils fuzzer, 2 conditions
      can happen in corrupted images, which can cause
      unexpected behaviors.
       - access the same pcluster one more time;
       - access the tail end pcluster again, e.g.
                  _ access again (will trigger tail merging)
                 |
           1 2 3 1 2             ->   1 2 3 1
           |_ tail end of the chain    \___/ (unexpected behavior)
      Let's detect and avoid them now.
      Reviewed-by: NChao Yu <yuchao0@huawei.com>
      Signed-off-by: NGao Xiang <gaoxiang25@huawei.com>
      Link: https://lore.kernel.org/r/20190821030908.40282-1-gaoxiang25@huawei.comSigned-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      bfc4ccb1
    • H
      2cb05d87
    • M