16 Jan, 2012

1 commit

  • This commit fixes a bug, while introducing a new one..

    commit 7203ddbd4be9720649e47d756a001e0c7d7f8ae2
    Author: Wang YanQing
    Date: Thu Jan 12 11:31:32 2012 +0800

    menuconfig: let make not report error when not save configuration

    Pressing ESC should cancel the yes/no dialog and return back to
    the main menu, but not exit from menuconfig.

    Signed-off-by: Li Zefan
    Acked-by: Wang YanQing
    Signed-off-by: Michal Marek

    Li Zefan
     

15 Jan, 2012

7 commits

  • Reinhard Tartler discovered a corner case of calling xfwrite() where the
    length of the string is zero.

    Arnaud Lacombe suggested to use assertion for the corner case, as
    fwrite(3) is currently used:

    1) in comment printers. Empty comment are not allowed.
    2) in a callback passed to expr_print(), where the string printed is
    either NULL OR non-empty.
    3) in the lexer, auto-generated, and unused.

    I feel using assertion is a good solution:

    1) It cleanly takes care of the above-mentioned corner case.
    2) It can be easily disabled by defining NDEBUG.
    3) It asserts xfwrite() is simply a wrapper for fwrite().

    Reported-by: Reinhard Tartler
    Signed-off-by: Arnaud Lacombe
    Signed-off-by: Jean Sacren
    Signed-off-by: Michal Marek

    Arnaud Lacombe
     
  • Make the V=0 output from update-po-config be aligned correctly.
    Also remove an outdated comment and add a "GEN" statement.

    Signed-off-by: Peter Foley
    Signed-off-by: Michal Marek

    Peter Foley
     
  • I find every time when I choice the 'NO' button at the dialog
    which let me choice whether to save the configuration before exit
    menuconfig, it always report the blow:

    " GEN /mnt/sda7/home/build/test/Makefile
    HOSTCC scripts/kconfig/mconf.o
    HOSTLD scripts/kconfig/mconf
    scripts/kconfig/mconf Kconfig

    Your configuration changes were NOT saved.

    make[2]: *** [menuconfig] Error 1
    make[1]: *** [menuconfig] Error 2
    make: *** [sub-make] Error 2 "

    This patch repair it.

    Signed-off-by: Wang YanQing
    Acked-by: Davidlohr Bueso
    Signed-off-by: Michal Marek

    Wang YanQing
     
  • Arnaud Lacombe pointed out the final checking that the requested configs
    were included in the final .config was broken.

    The example was that if you had a fragment that disabled
    CONFIG_DECOMPRESS_GZIP applied to a normal defconfig, there would be no
    final warning that CONFIG_DECOMPRESS_GZIP was acutally set in the final
    .config.

    This bug was introduced by me in v3 of the original patch, and the
    following patch reverts the invalid change.

    Signed-off-by: John Stultz
    Reported-by: Arnaud Lacombe
    Cc: Darren Hart
    Cc: Michal Marek
    Cc: Arnaud Lacombe
    Signed-off-by: Andrew Morton
    Signed-off-by: Michal Marek

    John Stultz
     
  • Fix whitespace usage in the clean_up routine.

    Signed-off-by: Darren Hart
    Acked-by: John Stultz
    Cc: Michal Marek
    Signed-off-by: Andrew Morton
    Signed-off-by: Michal Marek

    Darren Hart
     
  • The SIGHUP SIGINT and SIGTERM names caused failures when running
    merge_config.sh with the dash shell. Dropping the "SIG" component makes
    the script work in both bash and dash.

    Signed-off-by: Darren Hart
    Acked-by: John Stultz
    Cc: Michal Marek
    Signed-off-by: Andrew Morton
    Signed-off-by: Michal Marek

    Darren Hart
     
  • After noticing almost every distro has their own method of managing config
    fragments, I went looking at some best practices, and wanted to try to
    consolidate some of the different approaches so this fairly simple
    infrastructure can be shared (and new distros/build systems don't have to
    implement yet another config fragment merge script).

    This script is most influenced by the Windriver tools used in the Yocto
    Project, reusing some portions found there.

    This script merges multiple config fragments, warning on any overridden
    values. It then sets any unspecified values to their default, then
    finally checks to make sure no specified value was dropped due to
    unsatisfied dependencies.

    I'm sure this implementation won't work for everyone, and I expect it will
    need to evolve to adapt for various use cases. But I think its a
    reasonable starting point.

    Cc: Sam Ravnborg
    Cc: Greg Thelen
    Cc: Reinhard Tartler
    Cc: Dmitry Fink
    Cc: Darren Hart
    Cc: Eric B Munson
    Cc: Bruce Ashfield
    Cc: Michal Marek
    Signed-off-by: John Stultz
    Signed-off-by: Andrew Morton
    Signed-off-by: Michal Marek

    john stultz
     

19 Dec, 2011

1 commit

  • Use the xfwrite wrapper function defined in lkc.h to check the return value of
    fwrite and silence these warnings.

    HOSTCC scripts/kconfig/zconf.tab.o
    scripts/kconfig/zconf.tab.c: In function 'header_print_comment':
    /usr/src/lto/scripts/kconfig/confdata.c:551:10: warning: ignoring return value of 'fwrite', declared with attribute warn_unused_result
    scripts/kconfig/zconf.tab.c: In function 'kconfig_print_comment':
    /usr/src/lto/scripts/kconfig/confdata.c:467:10: warning: ignoring return value of 'fwrite', declared with attribute warn_unused_result

    Signed-off-by: Peter Foley
    Signed-off-by: Michal Marek

    Peter Foley
     

12 Dec, 2011

2 commits

  • Remove set but not used variables to fix warnings.

    HOSTCC scripts/kconfig/gconf.o
    /usr/src/lto/scripts/kconfig/gconf.c: In function 'change_sym_value':
    /usr/src/lto/scripts/kconfig/gconf.c:833:11: warning: variable 'oldval' set but not used [-Wunused-but-set-variable]
    /usr/src/lto/scripts/kconfig/gconf.c: In function 'update_tree':
    /usr/src/lto/scripts/kconfig/gconf.c:1281:19: warning: variable 'prop' set but not used [-Wunused-but-set-variable]

    Signed-off-by: Peter Foley
    Signed-off-by: Michal Marek

    Peter Foley
     
  • Specify format arguments to fix warnings.

    HOSTCC scripts/kconfig/gconf.o
    /usr/src/lto/scripts/kconfig/gconf.c: In function 'on_introduction1_activate':
    /usr/src/lto/scripts/kconfig/gconf.c:686:6: warning: format not a string literal and no format arguments
    /usr/src/lto/scripts/kconfig/gconf.c: In function 'on_about1_activate':
    /usr/src/lto/scripts/kconfig/gconf.c:704:6: warning: format not a string literal and no format arguments
    /usr/src/lto/scripts/kconfig/gconf.c: In function 'on_license1_activate':
    /usr/src/lto/scripts/kconfig/gconf.c:723:6: warning: format not a string literal and no format arguments

    Signed-off-by: Peter Foley
    Signed-off-by: Michal Marek

    Peter Foley
     

09 Sep, 2011

5 commits

  • to make it easier to locate begin/end when editing long strings;

    Signed-off-by: Cheng Renquan
    Acked By: Nir Tzachar

    Cheng Renquan
     
  • The original dialog_inputbox doesn't work with longer than prompt_width
    strings, here fixed it in this way:
    1) add variable cursor_form_win to record cursor of form_win,
    keep its value always between [0, prompt_width-1];
    reuse the original cursor_position as cursor of the string result,
    use (cursor_position-cursor_form_win) as begin offset to show part of
    the string in form_win;

    Signed-off-by: Cheng Renquan
    Cc: Arnaud Lacombe
    Cc: Nir Tzachar

    Cheng Renquan
     
  • To support unlimited length string config items;

    No check for realloc return value keeps code simple, and to be
    consistent with other existing unchecked malloc in kconfig.

    Signed-off-by: Cheng Renquan
    Signed-off-by: Arnaud Lacombe

    Cheng Renquan
     
  • In case KEY_BACKSPACE / KEY_DC to delete a char, it memmove only
    (len-cursor_position+1) bytes;
    the default case is to insert a char, it should also memmove exactly
    (len-cursor_position+1) bytes;

    the original use of (len+1) is wrong and may access following memory
    that doesn't belong to result, may cause SegFault in theory;

    case KEY_BACKSPACE:
    if (cursor_position > 0) {
    memmove(&result[cursor_position-1],
    &result[cursor_position],
    len-cursor_position+1);
    cursor_position--;
    }
    break;
    case KEY_DC:
    if (cursor_position >= 0 && cursor_position < len) {
    memmove(&result[cursor_position],
    &result[cursor_position+1],
    len-cursor_position+1);
    }
    break;
    default:
    if ((isgraph(res) || isspace(res)) &&
    len-2 < result_len) {
    /* insert the char at the proper position */
    memmove(&result[cursor_position+1],
    &result[cursor_position],
    len-cursor_position+1);
    result[cursor_position] = res;
    cursor_position++;
    }

    Signed-off-by: Cheng Renquan
    Acked-by: Nir Tzachar

    Cheng Renquan
     
  • Signed-off-by: Cheng Renquan
    Acked-by: Arnaud Lacombe

    Cheng Renquan
     

31 Aug, 2011

1 commit


30 Aug, 2011

3 commits


19 Aug, 2011

1 commit


08 Aug, 2011

13 commits


07 Aug, 2011

6 commits

  • After commit 3567866bf261: "RCUify freeing acls, let check_acl() go ahead in
    RCU mode if acl is cached" posix_acl_permission is being called with an
    unsupported flag and the permission check fails. This patch fixes the issue.

    Signed-off-by: Ari Savolainen
    Signed-off-by: Al Viro

    Ari Savolainen
     
  • * 'for-linus' of git://git.open-osd.org/linux-open-osd:
    ore: Make ore its own module
    exofs: Rename raid engine from exofs/ios.c => ore
    exofs: ios: Move to a per inode components & device-table
    exofs: Move exofs specific osd operations out of ios.c
    exofs: Add offset/length to exofs_get_io_state
    exofs: Fix truncate for the raid-groups case
    exofs: Small cleanup of exofs_fill_super
    exofs: BUG: Avoid sbi realloc
    exofs: Remove pnfs-osd private definitions
    nfs_xdr: Move nfs4_string definition out of #ifdef CONFIG_NFS_V4

    Linus Torvalds
     
  • The inode structure layout is largely random, and some of the vfs paths
    really do care. The path lookup in particular is already quite D$
    intensive, and profiles show that accessing the 'inode->i_op->xyz'
    fields is quite costly.

    We already optimized the dcache to not unnecessarily load the d_op
    structure for members that are often NULL using the DCACHE_OP_xyz bits
    in dentry->d_flags, and this does something very similar for the inode
    ops that are used during pathname lookup.

    It also re-orders the fields so that the fields accessed by 'stat' are
    together at the beginning of the inode structure, and roughly in the
    order accessed.

    The effect of this seems to be in the 1-2% range for an empty kernel
    "make -j" run (which is fairly kernel-intensive, mostly in filename
    lookup), so it's visible. The numbers are fairly noisy, though, and
    likely depend a lot on exact microarchitecture. So there's more tuning
    to be done.

    Signed-off-by: Linus Torvalds

    Linus Torvalds
     
  • Gcc tends to generate better code with small integers, including the
    DCACHE_xyz flag tests - so move the common ones to be first in the list.
    Also just remove the unused DCACHE_INOTIFY_PARENT_WATCHED and
    DCACHE_AUTOFS_PENDING values, their users no longer exists in the source
    tree.

    And add a "unlikely()" to the DCACHE_OP_COMPARE test, since we want the
    common case to be a nice straight-line fall-through.

    Signed-off-by: Linus Torvalds

    Linus Torvalds
     
  • * git://git.kernel.org/pub/scm/linux/kernel/git/davem/net:
    net: Compute protocol sequence numbers and fragment IDs using MD5.
    crypto: Move md5_transform to lib/md5.c

    Linus Torvalds
     
  • Export everything from ore need exporting. Change Kbuild and Kconfig
    to build ore.ko as an independent module. Import ore from exofs

    Signed-off-by: Boaz Harrosh

    Boaz Harrosh