All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: yamada.masahiro@socionext.com, linux-kbuild@vger.kernel.org
Cc: intel-gfx@lists.freedesktop.org
Subject: RE: [PATCH 1/2] kbuild: remove header compile test
Date: Thu, 19 Dec 2019 18:00:50 +0200	[thread overview]
Message-ID: <87tv5wwbil.fsf@intel.com> (raw)
In-Reply-To: <e13bb7e03399471d87230d2c6296c767@SOC-EX01V.e01.socionext.com>

On Fri, 08 Nov 2019, <yamada.masahiro@socionext.com> wrote:
> Could check the attached three patches?
>
> i915 is the only driver passionate about the header self-contained'ness.
> It would not be horrible to implement a own build rule in i915 Makefile.
>
> 0003 decreases the amount of code.
>
> 0001 and 0002 are trivial and can go in independently.
> ( I just send them to intel-gfx ML)

Sorry for the delayed response!

Thanks for doing this. I saw patches 1 and 2 were merged already.

I tweaked patch 3 slightly and resent it to intel-gfx [1].

BR,
Jani.


[1] http://patchwork.freedesktop.org/patch/msgid/20191219155652.2666-3-jani.nikula@intel.com


-- 
Jani Nikula, Intel Open Source Graphics Center

WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@intel.com>
To: yamada.masahiro@socionext.com, linux-kbuild@vger.kernel.org
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/2] kbuild: remove header compile test
Date: Thu, 19 Dec 2019 18:00:50 +0200	[thread overview]
Message-ID: <87tv5wwbil.fsf@intel.com> (raw)
In-Reply-To: <e13bb7e03399471d87230d2c6296c767@SOC-EX01V.e01.socionext.com>

On Fri, 08 Nov 2019, <yamada.masahiro@socionext.com> wrote:
> Could check the attached three patches?
>
> i915 is the only driver passionate about the header self-contained'ness.
> It would not be horrible to implement a own build rule in i915 Makefile.
>
> 0003 decreases the amount of code.
>
> 0001 and 0002 are trivial and can go in independently.
> ( I just send them to intel-gfx ML)

Sorry for the delayed response!

Thanks for doing this. I saw patches 1 and 2 were merged already.

I tweaked patch 3 slightly and resent it to intel-gfx [1].

BR,
Jani.


[1] http://patchwork.freedesktop.org/patch/msgid/20191219155652.2666-3-jani.nikula@intel.com


-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-12-19 16:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-07  7:14 [PATCH 1/2] kbuild: remove header compile test Masahiro Yamada
2019-11-07  7:14 ` [PATCH 2/2] kbuild: move headers_check rule to usr/include/Makefile Masahiro Yamada
2019-11-07  8:46 ` [PATCH 1/2] kbuild: remove header compile test Jani Nikula
2019-11-07  8:46   ` [Intel-gfx] " Jani Nikula
2019-11-08  5:38   ` yamada.masahiro
2019-11-08  5:38     ` [Intel-gfx] " yamada.masahiro
2019-11-08  5:38     ` yamada.masahiro
2019-12-19 16:00     ` Jani Nikula [this message]
2019-12-19 16:00       ` [Intel-gfx] " Jani Nikula

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=87tv5wwbil.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kbuild@vger.kernel.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.