This project is mirrored from git://git.denx.de/u-boot.git. The repository failed to update .
Repository mirroring has been paused due to too many failed attempts, and can be resumed by a project maintainer.
Last successful update .
  1. 04 Dec, 2017 1 commit
    • Masahiro Yamada's avatar
      mtd: nand: Rename nand.h into rawnand.h · 6ae3900a
      Masahiro Yamada authored
      This header was renamed to rawnand.h in Linux.
      
      The following is the corresponding commit in Linux.
      
        commit d4092d76a4a4e57b65910899948a83cc8646c5a5
        Author: Boris Brezillon <boris.brezillon@free-electrons.com>
        Date:   Fri Aug 4 17:29:10 2017 +0200
      
            mtd: nand: Rename nand.h into rawnand.h
      
            We are planning to share more code between different NAND based
            devices (SPI NAND, OneNAND and raw NANDs), but before doing that
            we need to move the existing include/linux/mtd/nand.h file into
            include/linux/mtd/rawnand.h so we can later create a nand.h header
            containing all common structure and function prototypes.
      Signed-off-by: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      6ae3900a
  2. 30 Nov, 2017 2 commits
  3. 21 Nov, 2017 1 commit
  4. 20 Nov, 2017 2 commits
  5. 23 Oct, 2017 1 commit
  6. 16 Oct, 2017 5 commits
  7. 08 Oct, 2017 2 commits
  8. 06 Oct, 2017 3 commits
  9. 04 Oct, 2017 1 commit
    • Masahiro Yamada's avatar
      treewide: replace with error() with pr_err() · 9b643e31
      Masahiro Yamada authored
      U-Boot widely uses error() as a bit noisier variant of printf().
      
      This macro causes name conflict with the following line in
      include/linux/compiler-gcc.h:
      
        # define __compiletime_error(message) __attribute__((error(message)))
      
      This prevents us from using __compiletime_error(), and makes it
      difficult to fully sync BUILD_BUG macros with Linux.  (Notice
      Linux's BUILD_BUG_ON_MSG is implemented by using compiletime_assert().)
      
      Let's convert error() into now treewide-available pr_err().
      
      Done with the help of Coccinelle, excluing tools/ directory.
      
      The semantic patch I used is as follows:
      
      // <smpl>
      @@@@
      -error
      +pr_err
       (...)
      // </smpl>
      Signed-off-by: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      Reviewed-by: default avatarSimon Glass <sjg@chromium.org>
      [trini: Re-run Coccinelle]
      Signed-off-by: Tom Rini's avatarTom Rini <trini@konsulko.com>
      9b643e31
  10. 03 Oct, 2017 6 commits
  11. 22 Sep, 2017 1 commit
    • Tom Rini's avatar
      fs/fat: Reduce stack usage · 2460098c
      Tom Rini authored
      We have limited stack in SPL builds.  Drop itrblock and move to
      malloc/free of itr to move this off of the stack.  As part of this fix a
      double-free issue in fat_size().
      Signed-off-by: Tom Rini's avatarTom Rini <trini@konsulko.com>
      ---
      Rework to use malloc/free as moving this to a global overflows some SH
      targets.
      2460098c
  12. 15 Sep, 2017 10 commits
  13. 26 Aug, 2017 2 commits
    • Tom Rini's avatar
      fs: ext4: Fix journal overrun issue reported by Coverity · 10b078d8
      Tom Rini authored
      While &p_jdb[fs->blksz] is a valid expression (it points *one* char
      sized element past the end of the array, e.g. &p_jdb[fs->blksz + 1] is
      invalid (according to the C standard (C99/C11)).
      
      Changing this to tag = (struct ext3_journal_block_tag *)(p_jdb + ofs);
      
      Cc: Stefan Brüns <stefan.bruens@rwth-aachen.de>
      Suggested-by: StefanBruens's avatarStefan Brüns <stefan.bruens@rwth-aachen.de>
      Reported-by: Coverity (CID: 165117, 165110)
      Signed-off-by: Tom Rini's avatarTom Rini <trini@konsulko.com>
      Reviewed-by: StefanBruens's avatarStefan Brüns <stefan.bruens@rwth-aachen.de>
      10b078d8
    • Reno Farnesi's avatar
      fs: fat: fix fatwrite overflow calculation · 76216211
      Reno Farnesi authored
      The overflow calculation was incorrect. Adding the start block of the
      partition is not needed because the sectors are already relative to the
      beginning of the partition. If you attempted to write a file smaller
      than cur_part_info.start blocks on a full partition the old calculation
      fails to catch the overflow. This would cause an infinite loop in the
      determine_fatent function.
      
      Old, incorrect calculation:
      
      ending sector of new file = start sector + file size (in sectors)
      last sector = partition start + total sectors on the partition
      
      Adding the partition start block number is not needed because sectors
      are already relative to the start of the partition.
      
      New calculation:
      
      ending sector of new file = start sector + file size (in sectors)
      last sector = total sectors on the partition
      Signed-off-by: default avatarReno Farnesi <nfarnesi4@gmail.com>
      76216211
  14. 20 Aug, 2017 1 commit
  15. 16 Aug, 2017 2 commits