public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ammar Faizi <ammarfaizi2@gnuweeb.org>
To: Marc Zyngier <maz@kernel.org>
Cc: kernel test robot <lkp@intel.com>,
	llvm@lists.linux.dev, kbuild-all@lists.01.org,
	GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
	linux-kernel@vger.kernel.org, Quentin Perret <qperret@google.com>,
	Alexandru Elisei <alexandru.elisei@arm.com>,
	Will Deacon <willdeacon@google.com>
Subject: Re: [ammarfaizi2-block:google/android/kernel/common/android12-5.10-2022-03 199/9999] arch/arm64/kvm/perf.c:58:36: error: implicit declaration of function 'perf_num_counters'
Date: Sat, 2 Apr 2022 17:44:49 +0700	[thread overview]
Message-ID: <60274552-dc33-e9ff-3fd8-d4d743a6f577@gnuweeb.org> (raw)
In-Reply-To: <87pmlzbyff.wl-maz@kernel.org>

Hi Marc,

On 4/2/22 4:57 PM, Marc Zyngier wrote:
> It doesn't bother me at all, and you shouldn't stop pushing stuff that
> is useful to you. My objection is to the testing of random trees and
> spamming of random people, specially when it is pretty obvious that
> the tree isn't targeting upstream Linux.
> 
> You really shouldn't change anything in your workflow on my account.

I sent a PR to lkp-tests to make the build error report private for my
google/android/.* branches. Should be good now.

https://github.com/intel/lkp-tests/pull/130

Thanks!

-- 
Ammar Faizi

      reply	other threads:[~2022-04-02 10:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-02  3:47 [ammarfaizi2-block:google/android/kernel/common/android12-5.10-2022-03 199/9999] arch/arm64/kvm/perf.c:58:36: error: implicit declaration of function 'perf_num_counters' kernel test robot
2022-04-02  9:38 ` Marc Zyngier
2022-04-02  9:52   ` Ammar Faizi
2022-04-02  9:57     ` Marc Zyngier
2022-04-02 10:44       ` Ammar Faizi [this message]

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=60274552-dc33-e9ff-3fd8-d4d743a6f577@gnuweeb.org \
    --to=ammarfaizi2@gnuweeb.org \
    --cc=alexandru.elisei@arm.com \
    --cc=gwml@vger.gnuweeb.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=maz@kernel.org \
    --cc=qperret@google.com \
    --cc=willdeacon@google.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