mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joao Pinto <Joao.Pinto@synopsys.com>
To: Kishon Vijay Abraham I <kishon@ti.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Jingoo Han <jingoohan1@gmail.com>,
	Joao Pinto <Joao.Pinto@synopsys.com>
Cc: <linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<nsekhar@ti.com>
Subject: Re: [PATCH] PCI: dwc: Add COMPILE_TEST to all designware based drivers
Date: Thu, 12 Jan 2017 16:46:31 +0000	[thread overview]
Message-ID: <d3743b45-a7de-f8a6-feeb-f6a2cd85d6f1@synopsys.com> (raw)
In-Reply-To: <1484214183-31805-1-git-send-email-kishon@ti.com>


Hi Kishon,

Às 9:43 AM de 1/12/2017, Kishon Vijay Abraham I escreveu:
> Add COMPILE_TEST to all designware based drivers so that it is possible
> to perform compile test even when a particular architecture specific
> config symbol is not set.
> 
> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
> ---
>  drivers/pci/dwc/Kconfig |   16 ++++++++--------
>  1 file changed, 8 insertions(+), 8 deletions(-)
> 

Your suggestion is interesting and I think it will improve the kbuild robot job,
since any change in a common file will be tested in all SoC specific drivers,
which does not happen at this moment.

This option is massively used across the kernel, and so it is a very welcome
addition to PCI in my opinion! Thanks.

Joao

  reply	other threads:[~2017-01-12 16:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-12  9:43 Kishon Vijay Abraham I
2017-01-12 16:46 ` Joao Pinto [this message]
     [not found] ` <CGME20170123084200epcas4p3433a190d7f9ef2c19ba008f62fab3c75@epcas4p3.samsung.com>
2017-01-23  8:44   ` pankaj.dubey

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=d3743b45-a7de-f8a6-feeb-f6a2cd85d6f1@synopsys.com \
    --to=joao.pinto@synopsys.com \
    --cc=bhelgaas@google.com \
    --cc=jingoohan1@gmail.com \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=nsekhar@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®