Eric Lee / smarc-fsl-linux-kernel

14 Jun, 2020

1 commit

  • a7f7f6248   treewide: replace '---help---' in Kconfig files with 'help' ... Browse Code »

    Since commit 84af7a6194e4 ("checkpatch: kconfig: prefer 'help' over
    '---help---'"), the number of '---help---' has been gradually
    decreasing, but there are still more than 2400 instances.

    This commit finishes the conversion. While I touched the lines,
    I also fixed the indentation.

    There are a variety of indentation styles found.

    a) 4 spaces + '---help---'
    b) 7 spaces + '---help---'
    c) 8 spaces + '---help---'
    d) 1 space + 1 tab + '---help---'
    e) 1 tab + '---help---' (correct indentation)
    f) 1 tab + 1 space + '---help---'
    g) 1 tab + 2 spaces + '---help---'

    In order to convert all of them to 1 tab + 'help', I ran the
    following commend:

    $ find . -name 'Kconfig*' | xargs sed -i 's/^[[:space:]]*---help---/\thelp/'

    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     

02 Nov, 2017

1 commit

  • b24413180   License cleanup: add SPDX GPL-2.0 license identifier to files with no license ... Browse Code »

    Many source files in the tree are missing licensing information, which
    makes it harder for compliance tools to determine the correct license.

    By default all files without license information are under the default
    license of the kernel, which is GPL version 2.

    Update the files which contain no license information with the 'GPL-2.0'
    SPDX license identifier. The SPDX identifier is a legally binding
    shorthand, which can be used instead of the full boiler plate text.

    This patch is based on work done by Thomas Gleixner and Kate Stewart and
    Philippe Ombredanne.

    How this work was done:

    Patches were generated and checked against linux-4.14-rc6 for a subset of
    the use cases:
    - file had no licensing information it it.
    - file was a */uapi/* one with no licensing information in it,
    - file was a */uapi/* one with existing licensing information,

    Further patches will be generated in subsequent months to fix up cases
    where non-standard license headers were used, and references to license
    had to be inferred by heuristics based on keywords.

    The analysis to determine which SPDX License Identifier to be applied to
    a file was done in a spreadsheet of side by side results from of the
    output of two independent scanners (ScanCode & Windriver) producing SPDX
    tag:value files created by Philippe Ombredanne. Philippe prepared the
    base worksheet, and did an initial spot review of a few 1000 files.

    The 4.13 kernel was the starting point of the analysis with 60,537 files
    assessed. Kate Stewart did a file by file comparison of the scanner
    results in the spreadsheet to determine which SPDX license identifier(s)
    to be applied to the file. She confirmed any determination that was not
    immediately clear with lawyers working with the Linux Foundation.

    Criteria used to select files for SPDX license identifier tagging was:
    - Files considered eligible had to be source code files.
    - Make and config files were included as candidates if they contained >5
    lines of source
    - File already had some variant of a license header in it (even if
    Reviewed-by: Philippe Ombredanne
    Reviewed-by: Thomas Gleixner
    Signed-off-by: Greg Kroah-Hartman

    Greg Kroah-Hartman
     

08 Oct, 2014

1 commit

  • 0223f9aae   Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k ... Browse Code »

    Pull m68k updates from Geert Uytterhoeven:
    "Summary:
    - a fix for an intermittent crash in macsonic and hilkbd, marked for
    stable,
    - build fixes for uncommon configs.

    Note: "m68k: AMIGA_BUILTIN_SERIAL should depend on TTY" was also
    picked up by GregKH for his TTY/Serial patches tree"

    * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k:
    m68k: Reformat arch/m68k/mm/hwtest.c
    m68k: Disable/restore interrupts in hwreg_present()/hwreg_write()
    m68k: AMIGA_BUILTIN_SERIAL should depend on TTY
    m68k: Add missing ioport_unmap()
    m68k/atari - stram: Add missing #include

    Linus Torvalds
     

28 Sep, 2014

1 commit

  • fd4d453b6   m68k: AMIGA_BUILTIN_SERIAL should depend on TTY ... Browse Code »

    If CONFIG_TTY=n:

    drivers/built-in.o: In function `rs_flush_buffer':
    amiserial.c:(.text+0x1f626): undefined reference to `tty_wakeup'
    drivers/built-in.o: In function `transmit_chars':
    amiserial.c:(.text+0x1f6c8): undefined reference to `tty_wakeup'
    drivers/built-in.o: In function `change_speed':
    amiserial.c:(.text+0x1f80a): undefined reference to `tty_termios_baud_rate'
    amiserial.c:(.text+0x1f88c): undefined reference to `tty_termios_baud_rate'
    drivers/built-in.o: In function `check_modem_status':
    amiserial.c:(.text+0x1faa6): undefined reference to `tty_hangup'
    amiserial.c:(.text+0x1faec): undefined reference to `tty_wakeup'
    drivers/built-in.o: In function `get_serial_info':
    amiserial.c:(.text+0x1fb88): undefined reference to `tty_lock'
    amiserial.c:(.text+0x1fbc0): undefined reference to `tty_unlock'
    drivers/built-in.o: In function `rs_open':
    amiserial.c:(.text+0x1fdc6): undefined reference to `tty_port_block_til_ready'
    drivers/built-in.o: In function `set_serial_info':
    amiserial.c:(.text+0x1fe0c): undefined reference to `tty_lock'
    amiserial.c:(.text+0x1fea0): undefined reference to `tty_unlock'
    amiserial.c:(.text+0x1fed0): undefined reference to `tty_unlock'
    amiserial.c:(.text+0x1ffaa): undefined reference to `tty_unlock'
    drivers/built-in.o: In function `receive_chars':
    amiserial.c:(.text+0x2005c): undefined reference to `do_SAK'
    amiserial.c:(.text+0x200e0): undefined reference to `tty_insert_flip_string_flags'
    amiserial.c:(.text+0x2013c): undefined reference to `tty_insert_flip_string_flags'
    amiserial.c:(.text+0x20148): undefined reference to `tty_flip_buffer_push'
    drivers/built-in.o: In function `rs_close':
    amiserial.c:(.text+0x20744): undefined reference to `tty_port_close_start'
    amiserial.c:(.text+0x2078a): undefined reference to `tty_ldisc_flush'
    amiserial.c:(.text+0x20798): undefined reference to `tty_port_close_end'
    drivers/built-in.o: In function `amiga_serial_probe':
    amiserial.c:(.init.text+0x96a): undefined reference to `__tty_alloc_driver'
    amiserial.c:(.init.text+0x9c0): undefined reference to `tty_std_termios'
    amiserial.c:(.init.text+0x9e6): undefined reference to `tty_set_operations'
    amiserial.c:(.init.text+0xa3e): undefined reference to `tty_port_init'
    amiserial.c:(.init.text+0xa5c): undefined reference to `tty_port_link_device'
    amiserial.c:(.init.text+0xa6c): undefined reference to `tty_register_driver'
    amiserial.c:(.init.text+0xb4a): undefined reference to `tty_unregister_driver'
    amiserial.c:(.init.text+0xb58): undefined reference to `tty_port_destroy'
    amiserial.c:(.init.text+0xb64): undefined reference to `put_tty_driver'

    Signed-off-by: Geert Uytterhoeven

    Geert Uytterhoeven
     

01 Sep, 2014

1 commit

17 Apr, 2013

2 commits

19 Jan, 2013

1 commit

  • 4f73bc4dd   tty: Added a CONFIG_TTY option to allow removal of TTY ... Browse Code »

    The option allows you to remove TTY and compile without errors. This
    saves space on systems that won't support TTY interfaces anyway.
    bloat-o-meter output is below.

    The bulk of this patch consists of Kconfig changes adding "depends on
    TTY" to various serial devices and similar drivers that require the TTY
    layer. Ideally, these dependencies would occur on a common intermediate
    symbol such as SERIO, but most drivers "select SERIO" rather than
    "depends on SERIO", and "select" does not respect dependencies.

    bloat-o-meter output comparing our previous minimal to new minimal by
    removing TTY. The list is filtered to not show removed entries with awk
    '$3 != "-"' as the list was very long.

    add/remove: 0/226 grow/shrink: 2/14 up/down: 6/-35356 (-35350)
    function old new delta
    chr_dev_init 166 170 +4
    allow_signal 80 82 +2
    static.__warned 143 142 -1
    disallow_signal 63 62 -1
    __set_special_pids 95 94 -1
    unregister_console 126 121 -5
    start_kernel 546 541 -5
    register_console 593 588 -5
    copy_from_user 45 40 -5
    sys_setsid 128 120 -8
    sys_vhangup 32 19 -13
    do_exit 1543 1526 -17
    bitmap_zero 60 40 -20
    arch_local_irq_save 137 117 -20
    release_task 674 652 -22
    static.spin_unlock_irqrestore 308 260 -48

    Signed-off-by: Joe Millenbach
    Reviewed-by: Jamey Sharp
    Reviewed-by: Josh Triplett
    Signed-off-by: Greg Kroah-Hartman

    Joe Millenbach
     

14 Nov, 2012

1 commit

  • 112f8b129   arch/m68k: remove CONFIG_EXPERIMENTAL ... Browse Code »

    This config item has not carried much meaning for a while now and is
    almost always enabled by default. As agreed during the Linux kernel
    summit, remove it.

    CC: Geert Uytterhoeven
    Signed-off-by: Kees Cook
    Signed-off-by: Geert Uytterhoeven

    Kees Cook
     

05 Jan, 2012

1 commit

29 Dec, 2011

1 commit

11 Dec, 2011

1 commit

09 Nov, 2011

1 commit

  • 24ed6ddd9   m68k: Revive lost ARAnyM config options ... Browse Code »

    commit 0e152d80507b75c00aac60f2ffc586360687cd52 ("m68k: reorganize Kconfig
    options to improve mmu/non-mmu selections") accidentally dropped the ARAnyM
    config options. Re-add them to the "Platform devices" section.

    Signed-off-by: Geert Uytterhoeven
    Acked-by: Greg Ungerer

    Geert Uytterhoeven
     

21 Oct, 2011

2 commits

18 Oct, 2011

1 commit

  • 0e152d805   m68k: reorganize Kconfig options to improve mmu/non-mmu selections ... Browse Code »

    The current mmu and non-mmu Kconfig files can be merged to form
    a more general selection of options. The current break up of options
    is due to the simple brute force merge from the m68k and m68knommu
    arch directories.

    Many of the options are not at all specific to having the MMU enabled
    or not. They are actually associated with a particular CPU type or
    platform type.

    Ultimately as we support all processors with the MMU disabled we need
    many of these options to be selectable without the MMU option enabled.
    And likewise some of the ColdFire processors, which currently are only
    supported with the MMU disabled, do have MMU hardware, and will need
    to have options selected on CPU type, not MMU disabled.

    This patch removes the old mmu and non-mmu Kconfigs and instead breaks
    up the configuration into four areas: cpu, machine, bus, devices.

    The Kconfig.cpu lists all the options associated with selecting a CPU,
    and includes options specific to each CPU type as well.

    Kconfig.machine lists all options associated with selecting a machine
    type. Almost always the machines selectable is restricted by the chosen
    CPU.

    Kconfig.bus contains options associated with selecting bus types on the
    various machine types. That includes PCI bus, PCMCIA bus, etc.

    Kconfig.devices contains options for drivers and driver associated
    options.

    Signed-off-by: Greg Ungerer

    Greg Ungerer