linux-kernel - Re: [PATCH 1/2] pci: Convert to use built-in RCU list checking

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Wed, 4 Sep 2019 22:36:43 +0300
From:   Andy Shevchenko <andy.shevchenko@...il.com>
To:     Joel Fernandes <joel@...lfernandes.org>
Cc:     kbuild test robot <lkp@...el.com>, kbuild-all@...org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Arnd Bergmann <arnd@...db.de>,
        Bjorn Helgaas <bhelgaas@...gle.com>,
        Catalin Marinas <catalin.marinas@....com>,
        "Gustavo A. R. Silva" <gustavo@...eddedor.com>,
        Jonathan Derrick <jonathan.derrick@...el.com>,
        Keith Busch <keith.busch@...el.com>, linux-pci@...r.kernel.org,
        Lorenzo Pieralisi <lorenzo.pieralisi@....com>
Subject: Re: [PATCH 1/2] pci: Convert to use built-in RCU list checking

On Wed, Sep 4, 2019 at 9:01 PM Joel Fernandes <joel@...lfernandes.org> wrote:
> On Wed, Sep 4, 2019 at 1:13 PM Andy Shevchenko
> <andy.shevchenko@...il.com> wrote:
> > On Wed, Sep 4, 2019 at 8:07 AM Joel Fernandes <joel@...lfernandes.org> wrote:
> > > On Wed, Sep 04, 2019 at 12:06:43PM +0800, kbuild test robot wrote:

> > > > [auto build test ERROR on linus/master]

^^^ (1)

> > > > [cannot apply to v5.3-rc7 next-20190903]

^^^ (2)


> The dependency is already in -next and I pulled it and applied the
> patch.

This is a problem. You must provide dependency even for maintainers
(in form of immutable branch / tag).
The easier way to provide Depends-on (when it's one patch), though
kbuild bot doesn't support it. Yet?

>  It is testing -next right?

It testing (1) and (2). (it was unable to apply against next by some
reason, but the build error is against latest vanilla failed. And this
is completely correct. Just follow the process (see above).

-- 
With Best Regards,
Andy Shevchenko