linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rong Chen <rong.a.chen@intel.com>
To: Daniel Palmer <daniel@0x0f.com>, kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [kbuild-all] Re: [linux-chenxing:mstar_v5_14_rebase_i2_drm 257/349] drivers/clk/mstar/clk-msc313-mux.c:27:2: error: implicit declaration of function 'regmap_field_read'; did you mean 'regmap_field_write'?
Date: Mon, 19 Jul 2021 16:42:57 +0800	[thread overview]
Message-ID: <4280701c-4051-89a5-c280-4765193d518e@intel.com> (raw)
In-Reply-To: <CAFr9PXng3dVVeHm8Xcy3i7MfjnPOM8ewCtGAWWUcgBZcM+RJqw@mail.gmail.com>



On 7/19/21 1:17 PM, Daniel Palmer wrote:
> On Mon, 19 Jul 2021 at 03:52, kernel test robot <lkp@intel.com> wrote:
>> tree:   git://github.com/linux-chenxing/linux.git mstar_v5_14_rebase_i2_drm
> Is it possible to stop this bot from building branches that don't make
> any sense?

Hi Daniel,

Thanks for the advice, we'll stop testing such 'rebase' branches.

Best Regards,
Rong Chen


> This branch for example was a work branch for reverse engineering the
> display hardware and has a lot of junk in it.
>
> Cheers,
>
> Daniel


      reply	other threads:[~2021-07-19  9:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-18 18:52 [linux-chenxing:mstar_v5_14_rebase_i2_drm 257/349] drivers/clk/mstar/clk-msc313-mux.c:27:2: error: implicit declaration of function 'regmap_field_read'; did you mean 'regmap_field_write'? kernel test robot
2021-07-19  5:17 ` Daniel Palmer
2021-07-19  8:42   ` Rong Chen [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=4280701c-4051-89a5-c280-4765193d518e@intel.com \
    --to=rong.a.chen@intel.com \
    --cc=daniel@0x0f.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.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;
as well as URLs for NNTP newsgroup(s).