linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re:..build stopped... Linux 5.9-rc1
Date: Mon, 17 Aug 2020 04:28:25 +0530	[thread overview]
Message-ID: <20200816225822.GA3222@debian> (raw)
In-Reply-To: <CAHk-=wiwfkKp93C+yLqKWAU0ChBdeBDUhgOk09_=UQ8gOKbV3w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 10229 bytes --]

On 13:50 Sun 16 Aug 2020, Linus Torvalds wrote:
>This merge window felt a lot more normal than 5.8, and all the stats
>confirm thar it seems to be the usual size.
>
>The only thing that stands out is yet another AMD GPU header file
>drop, but by now that almost counts as "usual" too. It does mean that
>the diff stats are dominated by those AMD updates, and almost exactly
>half of the diff is under drivers/gpu/drm/amd/, but it's the usual big
>register definitions (presumably once more generated from the hw
>files) and doesn't really matter in the big picture.
>
>If you ignore that, stats look very normal. Even ignoring the AMD GPU
>updates, drivers are still about 60% of the patch, and it's all over.
>Outside of drivers, it's the usual mix of architecture updates,
>documentation, core networking, tooling and filesystem updates.
>
>"Normal size" is still obviously pretty big, so the appended is just
>my merge-log as usual. For details, dig down into whichever area
>excites you in the git tree...
>
>                      Linus
>

I am scared that I might have missed something very obvious ...am I?? And the build abort...take a peek..

In file included from ./include/linux/scatterlist.h:9,
                 from ./include/linux/blkdev.h:25,
                 from ./include/linux/blk-cgroup.h:23,
                 from ./include/linux/writeback.h:14,
                 from ./include/linux/memcontrol.h:22,
                 from ./include/linux/swap.h:9,
                 from ./include/linux/suspend.h:5,
                 from arch/x86/kernel/asm-offsets.c:13:
./arch/x86/include/asm/io.h: In function ‘outb_p’:
./arch/x86/include/asm/io.h:292:2: error: implicit declaration of function ‘slow_down_io’ [-Werror=implicit-function-declaration]
  slow_down_io();       \
  ^~~~~~~~~~~~
./arch/x86/include/asm/io.h:334:1: note: in expansion of macro ‘BUILDIO’
 BUILDIO(b, b, char)
 ^~~~~~~
In file included from ./arch/x86/include/asm/suspend_64.h:10,
                 from ./arch/x86/include/asm/suspend.h:5,
                 from arch/x86/kernel/asm-offsets.c:19:
./arch/x86/include/asm/desc.h: In function ‘__set_tss_desc’:
./arch/x86/include/asm/desc.h:186:2: error: implicit declaration of function ‘write_gdt_entry’; did you mean ‘find_get_entry’? [-Werror=implicit-function-declaration]
  write_gdt_entry(d, entry, &tss, DESC_TSS);
  ^~~~~~~~~~~~~~~
  find_get_entry
./arch/x86/include/asm/desc.h: In function ‘force_reload_TR’:
./arch/x86/include/asm/desc.h:296:2: error: implicit declaration of function ‘load_TR_desc’; did you mean ‘local_dec’? [-Werror=implicit-function-declaration]
  load_TR_desc();
  ^~~~~~~~~~~~
  local_dec
./arch/x86/include/asm/desc.h: In function ‘clear_LDT’:
./arch/x86/include/asm/desc.h:358:2: error: implicit declaration of function ‘set_ldt’; did you mean ‘set_bit’? [-Werror=implicit-function-declaration]
  set_ldt(NULL, 0);
  ^~~~~~~
  set_bit
cc1: some warnings being treated as errors
make[1]: *** [scripts/Makefile.build:117: arch/x86/kernel/asm-offsets.s] Error 1

~Bhaskar
>---
>
>Al Viro (6):
>    ptrace regset updates
>    init and set_fs() cleanups
>    fdpick coredump update
>    mount leak fix
>    misc vfs updates
>    regset conversion fix
>
>Alex Williamson (1):
>    VFIO updates
>
>Alexandre Belloni (1):
>    RTC updates
>
>Andreas Gruenbacher (1):
>    gfs2 updates
>
>Andrew Morton (3):
>    misc updates
>    more updates
>    even more updates
>
>Andy Shevchenko (1):
>    x86 platform driver updates
>
>Arnaldo Carvalho de Melo (2):
>    perf tools updates
>    more perf tools updates
>
>Arnd Bergmann (5):
>    ARM defconfig updates
>    ARM SoC DT updates
>    ARM SoC updates
>    ARM SoC driver updates
>    new ARM SoC support
>
>Benson Leung (1):
>    chrome platform updates
>
>Bjorn Andersson (3):
>    rpmsg update
>    remoteproc updates
>    hwspinlock updates
>
>Bjorn Helgaas (1):
>    PCI updates
>
>Casey Schaufler (1):
>    smack updates
>
>Catalin Marinas (3):
>    arm64 and cross-arch updates
>    arm64 fixes
>    arm64 fix
>
>Christian Brauner (4):
>    thread updates
>    fork cleanups
>    checkpoint-restore updates
>    close_range() implementation
>
>Christoph Hellwig (2):
>    uuid update
>    dma-mapping updates
>
>Chuck Lever (1):
>    NFS server updates
>
>Corey Minyard (1):
>    IPMI updates
>
>Damien Le Moal (1):
>    zonefs update
>
>Daniel Lezcano (1):
>    thermal updates
>
>Darrick Wong (3):
>    iomap updates
>    xfs updates
>    xfs fixes
>
>Dave Airlie (2):
>    drm updates
>    drm fixes
>
>David Miller (2):
>    networking updates
>    networking fixes
>
>David Sterba (2):
>    btrfs updates
>    more btrfs updates
>
>David Teigland (1):
>    dlm updates
>
>Dmitry Torokhov (1):
>    input updates
>
>Dominique Martinet (1):
>    9p updates
>
>Eric Biederman (1):
>    execve updates
>
>Eric Biggers (2):
>    fscrypt updates
>    fsverity update
>
>Gao Xiang (1):
>    erofs updates
>
>Geert Uytterhoeven (1):
>    m68k updates
>
>Greg KH (5):
>    char/misc driver updates
>    driver core updates
>    USB/Thunderbolt updates
>    staging/IIO driver updates
>    tty/serial updates
>
>Greg Ungerer (1):
>    m68knommu updates
>
>Guenter Roeck (1):
>    hwmon updates
>
>Guo Ren (1):
>    arch/csky updates
>
>Heiko Carstens (2):
>    s390 updates
>    more s390 updates
>
>Helge Deller (2):
>    parisc updates
>    more parisc updates
>
>Herbert Xu (2):
>    crypto updates
>    crypto fix
>
>Ilya Dryomov (1):
>    ceph updates
>
>Ingo Molar (1):
>    x86 cpu updates
>
>Ingo Molnar (26):
>    irq fixes
>    debugobjects cleanup
>    header cleanup
>    RCU updates
>    locking updates
>    objtool updates
>    perf event updates
>    scheduler updates
>    x86/alternatives update
>    x86 asm updates
>    x86 boot updates
>    x86 build updates
>    x86 cleanups
>    x86 debug fixlets
>    x86 FPU selftest
>    x86 microcode update
>    x86 MSR filtering
>    x86 mmm update
>    x86 platform updates
>    x86 timer update
>    x86 RAS updates
>    sched/fifo updates
>    locking fixlets
>    perf fixes
>    scheduler fixes
>    x86 fixes
>
>Jaegeuk Kim (1):
>    f2fs updates
>
>James Bottomley (2):
>    SCSI updates
>    more SCSI updates
>
>James Morris (1):
>    security subsystem updates
>
>Jan Kara (2):
>    ext2, udf, reiserfs, quota cleanups and minor fixes
>    fsnotify updates
>
>Jarkko Sakkinen (1):
>    tpm updates
>
>Jason Gunthorpe (2):
>    hmm updates
>    rdma updates
>
>Jassi Brar (1):
>    mailbox updates
>
>Jeff Layton (1):
>    file locking fix
>
>Jens Axboe (6):
>    core block updates
>    io_uring updates
>    block driver updates
>    block stacking updates
>    block fixes
>    io_uring fixes
>
>Jessica Yu (1):
>    module updates
>
>Jiri Kosina (1):
>    HID updates
>
>Joerg Roedel (1):
>    iommu updates
>
>Jonathan Corbet (2):
>    documentation updates
>    documentation fixes
>
>Juergen Gross (2):
>    xen updates
>    more xen updates
>
>Julia Lawall (1):
>    coccinelle updates
>
>Kees Cook (8):
>    pstore update
>    gcc plugin updates
>    automatic variable initialization updates
>    tasklets API update
>    uninitialized_var() macro removal
>    seccomp updates
>    seccomp fix
>    sysfs module section fix
>
>Lee Jones (2):
>    backlight updates
>    MFD updates
>
>Linus Walleij (2):
>    GPIO updates
>    pin control updates
>
>Mark Brown (3):
>    regulator updates
>    spi updates
>    regmap updates
>
>Masahiro Yamada (2):
>    Kbuild updates
>    Kconfig updates
>
>Mauro Carvalho Chehab (1):
>    media updates
>
>Max Filippov (1):
>    Xtensa updates
>
>Michael Ellerman (2):
>    powerpc updates
>    powerpc fix
>
>Michael Tsirkin (1):
>    virtio updates
>
>Miguel Ojeda (1):
>    auxdisplay update
>
>Mike Marshall (1):
>    orangefs updates
>
>Mike Rapoport (1):
>    unicore32 removal
>
>Mike Snitzer (1):
>    device mapper updates
>
>Mimi Zohar (1):
>    integrity updates
>
>Miquel Raynal (1):
>    mtd updates
>
>Namjae Jeon (1):
>    exfat updates
>
>Palmer Dabbelt (2):
>    RISC-V updates
>    RISC-V fix
>
>Paolo Bonzini (2):
>    KVM updates
>    more KVM updates
>
>Paul Moore (2):
>    selinux updates
>    audit updates
>
>Pavel Machek (1):
>    LED updates
>
>Petr Mladek (2):
>    printk updates
>    livepatching updates
>
>Rafael Wysocki (5):
>    power management updates
>    ACPI updates
>    more power management updates
>    one more power management update
>    more ACPI updates
>
>Rich Felker (1):
>    arch/sh updates
>
>Richard Weinberger (2):
>    mtd fix
>    JFFS2, UBI and UBIFS updates
>
>Rob Herring (2):
>    Devicetree updates
>    devicetree fixes
>
>Russell King (1):
>    ARM updates
>
>Sebastian Reichel (1):
>    power supply and reset updates
>
>Shuah Khan (1):
>    kunit updates
>
>Stafford Horne (1):
>    OpenRISC updates
>
>Stephen Boyd (2):
>    clk updates
>    more clk updates
>
>Steve French (2):
>    cifs updates
>    cifs fixes
>
>Steven Rostedt (2):
>    tracing updates
>    ktest updates
>
>Takashi Iwai (2):
>    sound updates
>    sound fixes
>
>Thierry Reding (1):
>    pwm updates
>
>Thomas Bogendoerfer (1):
>    MIPS upates
>
>Thomas Gleixner (9):
>    irq updates
>    timer updates
>    generic kernel entry/exit code
>    x86 conversion to generic entry code
>    x86 fsgsbase
>    locking updates
>    irq fixes
>    more timer updates
>    timekeeping updates
>
>Tony Luck (2):
>    EDAC updates
>    edac fix
>
>Trond Myklebust (1):
>    NFS client updates
>
>Ulf Hansson (1):
>    MMC updates
>
>Vinod Koul (1):
>    dmaengine updates
>
>Vishal Verma (1):
>    libnvdimm updayes
>
>Wei Liu (2):
>    hyperv updates
>    hyper-v fixes
>
>Wim Van Sebroeck (1):
>    watchdog updates
>
>Wolfram Sang (1):
>    i2c updates

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-08-16 22:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-16 20:50 Linux 5.9-rc1 Linus Torvalds
2020-08-16 22:58 ` Bhaskar Chowdhury [this message]
2020-08-17 16:44   ` ..build stopped... " Linus Torvalds
2020-08-17 21:25     ` .config file attached for your perusal..build " Bhaskar Chowdhury
2020-08-17 23:22       ` Randy Dunlap
2020-08-17 23:32       ` Linus Torvalds
2020-08-18  0:43         ` Bhaskar Chowdhury
2020-08-17  1:35 ` Linux 5.9-rc1 (sparse? kernel/time/timekeeping.c) Randy Dunlap
2020-08-17  2:15   ` Luc Van Oostenryck
2020-08-17  2:17     ` Randy Dunlap

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200816225822.GA3222@debian \
    --to=unixbhaskar@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).