All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-spdx@vger.kernel.org
Subject: Re: [GIT PULL] SPDX update for 5.2-rc3 - round 2
Date: Mon, 3 Jun 2019 09:38:33 +0200	[thread overview]
Message-ID: <20190603073833.GA20329@kroah.com> (raw)
In-Reply-To: <CAK7LNARDyZ1pKHwiHsOntbc9oxbGHgbD+tptEF4a0VC3GvAyTA@mail.gmail.com>

On Mon, Jun 03, 2019 at 09:15:08AM +0900, Masahiro Yamada wrote:
> On Mon, Jun 3, 2019 at 2:15 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Sun, Jun 02, 2019 at 09:03:46PM +0900, Masahiro Yamada wrote:
> > > On Sun, Jun 2, 2019 at 4:17 PM Greg KH <gregkh@linuxfoundation.org> wrote:
> > > >
> > > > The following changes since commit 2f4c53349961c8ca480193e47da4d44fdb8335a8:
> > > >
> > > >   Merge tag 'spdx-5.2-rc3-1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core (2019-05-31 08:34:32 -0700)
> > > >
> > > > are available in the Git repository at:
> > > >
> > > >   git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git tags/spdx-5.2-rc3-2
> > > >
> > > > for you to fetch changes up to 8e82fe2ab65a80b1526b285c661ab88cc5891e3a:
> > > >
> > > >   treewide: fix typos of SPDX-License-Identifier (2019-06-01 18:29:58 +0200)
> > > >
> > > > ----------------------------------------------------------------
> > > > SPDX fixes for 5.2-rc3, round 2
> > > >
> > > > Here are just two small patches, that fix up some found SPDX identifier
> > > > issues.
> > > >
> > > > The first patch fixes an error in a previous SPDX fixup patch, that
> > > > causes build errors when doing 'make clean' on the tree (the fact that
> > > > almost no one noticed it reflects the fact that kernel developers don't
> > > > like doing that option very often...)
> > >
> > > This paragraph is not precise.
> > >
> > > Not only "make clean", but also the normal build is broken.
> > > In fact, ARCH=arm allmodconfig is broken.
> > >
> > >
> > > $ make -j8 ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- allmodconfig
> > >   [ snip ]
> > > $ make -j8 ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf-
> > >   [ snip ]
> > > drivers/crypto/ux500/cryp/Makefile:5: *** missing separator.  Stop.
> > > make[3]: *** [scripts/Makefile.build;489: drivers/crypto/ux500/cryp] Error 2
> > > make[2]: *** [scripts/Makefile.build;489: drivers/crypto/ux500] Error 2
> > > make[1]: *** [scripts/Makefile.build;489: drivers/crypto] Error 2
> > > make[1]: *** Waiting for unfinished jobs....
> > >
> > >
> > >
> > > The 0-day bot should check allmodconfig for all arches,
> > > but surprisingly it was not caught before the merge.
> >
> > Ah, good catch, odd that 0-day missed it.  Maybe it is not building
> > 32bit builds these days :(
> 
> 
> I noticed the SPDX patches were submitted to
> linux-spdx@vger.kernel.org
> but not to linux-kernel@vger.kernel.org
> 
> Maybe, the reason is why 0-day bot is not subscribing to
> linux-spdx@vger.kernel.org
> 
> 
> You picked up them and sent a pull request immediately,
> so the 0-day bot was not given time to test your branch either.

No, I got a response from the 0-day bot, it said it tested my branch but
timed out doing more tests because it was busy.  It seems the bot is not
working that well at the moment as it is giving me this same "limited"
testing for all of my trees right now :(

> >> Not all developers run scripts/checkpatch.pl before patch submission.
> >> Not all maintainers run scripts/checkpatch.pl before commit.
> >
> >Very true :(
> 
> 
> If we really want to improve the situation,
> perhaps can we ask Intel to run scripts/checkpatch.pl in the 0-day bot?
> 
> checkpatch.pl may warn false positives,
> but at least "Missing or malformed SPDX-License-Identifier tag"
> is a good checker.  Just my two cents.

Sounds like something good to be added to 0-day, please propose it to
the developers.  But let them fix whatever is currently not working with
it first :)

thanks,

greg k-h

  reply	other threads:[~2019-06-03  7:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-02  6:39 [GIT PULL] SPDX update for 5.2-rc3 - round 2 Greg KH
2019-06-02 12:03 ` Masahiro Yamada
2019-06-02 17:15   ` Greg KH
2019-06-03  0:15     ` Masahiro Yamada
2019-06-03  7:38       ` Greg KH [this message]
2019-06-02 15:04 ` Joe Perches
2019-06-02 17:25 ` pr-tracker-bot

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=20190603073833.GA20329@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spdx@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=yamada.masahiro@socionext.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.