linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: Re: [GIT PULL] Kbuild updates for v6.1-rc1
Date: Fri, 14 Oct 2022 11:49:30 +0200	[thread overview]
Message-ID: <20221014094930.GB13389@twin.jikos.cz> (raw)
In-Reply-To: <CAK7LNASzGEiQfPTaLmhG4k7VAwB5yznd-VqWdJHEF2YjgSQTcA@mail.gmail.com>

On Thu, Oct 06, 2022 at 11:29:44PM +0900, Masahiro Yamada wrote:
> Masahiro Yamada (35):
>       kbuild: remove the target in signal traps when interrupted
>       kbuild: add phony targets to ./Kbuild
>       kbuild: hard-code KBUILD_ALLDIRS in scripts/Makefile.package
>       kbuild: check sha1sum just once for each atomic header
>       kbuild: do not deduplicate modules.order
>       nios2: move core-y in arch/nios2/Makefile to arch/nios2/Kbuild
>       kbuild: remove duplicated dependency between modules and modules_check

This patch merged as f75a03340c2c2eea772e4d59412135021afea493 breaks
build of modules when it's specified by path like 'make fs/btrfs/'. The
'make M=fs/btrfs' works but I don't see any reason why the former should
stop working. Also the patch does not mention anything like that so it's
most likely a bug.

  parent reply	other threads:[~2022-10-14  9:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-06 14:29 [GIT PULL] Kbuild updates for v6.1-rc1 Masahiro Yamada
2022-10-10 19:52 ` Masahiro Yamada
2022-10-10 19:57   ` Linus Torvalds
2022-10-10 20:05 ` pr-tracker-bot
2022-10-14  9:49 ` David Sterba [this message]
2022-10-14 10:06   ` David Sterba
2022-10-14 12:45     ` Masahiro Yamada

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=20221014094930.GB13389@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@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).