linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rong Chen <rong.a.chen@intel.com>
To: Marc Zyngier <maz@kernel.org>, kernel test robot <lkp@intel.com>
Cc: irqchip-bot for Marc Zyngier <tip-bot2@linutronix.de>,
	linux-kernel@vger.kernel.org, kbuild-all@lists.01.org,
	tglx@linutronix.de
Subject: Re: [kbuild-all] Re: [irqchip: irq/irqchip-next] powerpc: Drop dependency between asm/irq.h and linux/irqdomain.h
Date: Mon, 7 Jun 2021 14:34:39 +0800	[thread overview]
Message-ID: <1dbed936-a112-8493-aab2-bbf87aaf6cc2@intel.com> (raw)
In-Reply-To: <0daef13c3e27002d10bedb7f9719d633@kernel.org>



On 6/6/21 11:24 PM, Marc Zyngier wrote:
> On 2021-06-06 16:00, kernel test robot wrote:
>> Hi irqchip-bot,
>>
>> Thank you for the patch! Yet something to improve:
>>
>> [auto build test ERROR on powerpc/next]
>> [also build test ERROR on linux/master linus/master v5.13-rc4 
>> next-20210604]
>> [If your patch is applied to the wrong git tree, kindly drop us a note.
>> And when submitting patch, we suggest to use '--base' as documented in
>> https://git-scm.com/docs/git-format-patch]
>>
>> url:
>> https://github.com/0day-ci/linux/commits/irqchip-bot-for-Marc-Zyngier/powerpc-Drop-dependency-between-asm-irq-h-and-linux-irqdomain-h/20210606-205106 
>>
>> base: 
>> https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next
>> config: powerpc-sbc8548_defconfig (attached as .config)
>> compiler: powerpc-linux-gcc (GCC) 9.3.0
>> reproduce (this is a W=1 build):
>>         wget
>> https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross
>> -O ~/bin/make.cross
>>         chmod +x ~/bin/make.cross
>>         #
>> https://github.com/0day-ci/linux/commit/72415db4cc9ec9987380123553c3222a3568f37f 
>>
>>         git remote add linux-review https://github.com/0day-ci/linux
>>         git fetch --no-tags linux-review
>> irqchip-bot-for-Marc-Zyngier/powerpc-Drop-dependency-between-asm-irq-h-and-linux-irqdomain-h/20210606-205106 
>>
>>         git checkout 72415db4cc9ec9987380123553c3222a3568f37f
>
> I got curious, and fetched this tree. This patch is isolated,
> out of context in the series, and makes absolutely zero sense
> on its own. No wonder you detect all sort of compilation issues.
>
> If you are going to test things, please pick the whole branch,
> and not random patches. This is a waste of everybody's time.
>
>         M.

Hi Marc,

Sorry for the inconvenience, we didn't identify the patch emails from 
tip-bot2,
we'll ignore these emails to avoid ineffective work.

Best Regards,
Rong Chen

  reply	other threads:[~2021-06-07  6:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-06 12:43 [irqchip: irq/irqchip-next] powerpc: Drop dependency between asm/irq.h and linux/irqdomain.h irqchip-bot for Marc Zyngier
2021-06-06 15:00 ` kernel test robot
2021-06-06 15:24   ` Marc Zyngier
2021-06-07  6:34     ` Rong Chen [this message]
2021-06-06 15:28 ` kernel test robot

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=1dbed936-a112-8493-aab2-bbf87aaf6cc2@intel.com \
    --to=rong.a.chen@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=maz@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tip-bot2@linutronix.de \
    /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).