From: Rob Herring <robh@kernel.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: devicetree@vger.kernel.org,
Michal Marek <michal.lkml@markovi.net>,
linux-kbuild@vger.kernel.org, David Airlie <airlied@linux.ie>,
Jan Kiszka <jan.kiszka@siemens.com>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Kieran Bingham <kbingham@kernel.org>
Subject: Re: [Intel-gfx] [PATCH] kbuild: use always-y instead of extra-y
Date: Wed, 20 Jan 2021 15:39:29 -0600 [thread overview]
Message-ID: <20210120213929.GA875847@robh.at.kernel.org> (raw)
In-Reply-To: <20210120062351.3011786-1-masahiroy@kernel.org>
On Wed, Jan 20, 2021 at 03:23:51PM +0900, Masahiro Yamada wrote:
> As commit d0e628cd817f ("kbuild: doc: clarify the difference between
> extra-y and always-y") explained, extra-y should be used for listing
> the prerequsites of vmlinux. always-y is a better fix here.
prerequisites
Glad to see this clarified. I think just tried both and picked one.
Reviewed-by: Rob Herring <robh@kernel.org>
>
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
> ---
>
> Documentation/devicetree/bindings/Makefile | 8 ++++----
> drivers/gpu/drm/i915/Makefile | 2 +-
> scripts/Makefile.lib | 10 +++++-----
> scripts/gdb/linux/Makefile | 2 +-
> 4 files changed, 11 insertions(+), 11 deletions(-)
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-kbuild@vger.kernel.org, Daniel Vetter <daniel@ffwll.ch>,
David Airlie <airlied@linux.ie>,
Jan Kiszka <jan.kiszka@siemens.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Kieran Bingham <kbingham@kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kbuild: use always-y instead of extra-y
Date: Wed, 20 Jan 2021 15:39:29 -0600 [thread overview]
Message-ID: <20210120213929.GA875847@robh.at.kernel.org> (raw)
In-Reply-To: <20210120062351.3011786-1-masahiroy@kernel.org>
On Wed, Jan 20, 2021 at 03:23:51PM +0900, Masahiro Yamada wrote:
> As commit d0e628cd817f ("kbuild: doc: clarify the difference between
> extra-y and always-y") explained, extra-y should be used for listing
> the prerequsites of vmlinux. always-y is a better fix here.
prerequisites
Glad to see this clarified. I think just tried both and picked one.
Reviewed-by: Rob Herring <robh@kernel.org>
>
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
> ---
>
> Documentation/devicetree/bindings/Makefile | 8 ++++----
> drivers/gpu/drm/i915/Makefile | 2 +-
> scripts/Makefile.lib | 10 +++++-----
> scripts/gdb/linux/Makefile | 2 +-
> 4 files changed, 11 insertions(+), 11 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: devicetree@vger.kernel.org,
Michal Marek <michal.lkml@markovi.net>,
linux-kbuild@vger.kernel.org, David Airlie <airlied@linux.ie>,
Jan Kiszka <jan.kiszka@siemens.com>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
dri-devel@lists.freedesktop.org,
Kieran Bingham <kbingham@kernel.org>
Subject: Re: [PATCH] kbuild: use always-y instead of extra-y
Date: Wed, 20 Jan 2021 15:39:29 -0600 [thread overview]
Message-ID: <20210120213929.GA875847@robh.at.kernel.org> (raw)
In-Reply-To: <20210120062351.3011786-1-masahiroy@kernel.org>
On Wed, Jan 20, 2021 at 03:23:51PM +0900, Masahiro Yamada wrote:
> As commit d0e628cd817f ("kbuild: doc: clarify the difference between
> extra-y and always-y") explained, extra-y should be used for listing
> the prerequsites of vmlinux. always-y is a better fix here.
prerequisites
Glad to see this clarified. I think just tried both and picked one.
Reviewed-by: Rob Herring <robh@kernel.org>
>
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
> ---
>
> Documentation/devicetree/bindings/Makefile | 8 ++++----
> drivers/gpu/drm/i915/Makefile | 2 +-
> scripts/Makefile.lib | 10 +++++-----
> scripts/gdb/linux/Makefile | 2 +-
> 4 files changed, 11 insertions(+), 11 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2021-01-20 21:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 6:23 [Intel-gfx] [PATCH] kbuild: use always-y instead of extra-y Masahiro Yamada
2021-01-20 6:23 ` Masahiro Yamada
2021-01-20 6:23 ` Masahiro Yamada
2021-01-20 21:39 ` Rob Herring [this message]
2021-01-20 21:39 ` Rob Herring
2021-01-20 21:39 ` Rob Herring
2021-01-26 18:35 ` [Intel-gfx] " Masahiro Yamada
2021-01-26 18:35 ` Masahiro Yamada
2021-01-26 18:35 ` Masahiro Yamada
2021-01-20 22:08 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for " Patchwork
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=20210120213929.GA875847@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=airlied@linux.ie \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jan.kiszka@siemens.com \
--cc=kbingham@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
/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.