Linux wireless drivers development
 help / color / mirror / Atom feed
From: Rong Chen <rong.a.chen@intel.com>
To: Adham.Abozaeid@microchip.com, lkp@intel.com
Cc: devel@driverdev.osuosl.org, Ajay.Kathat@microchip.com,
	gregkh@linuxfoundation.org, linux-wireless@vger.kernel.org,
	kbuild-all@01.org, Eugen.Hristev@microchip.com,
	johannes@sipsolutions.net
Subject: Re: [kbuild-all] [PATCH] staging: wilc1000: look for rtc_clk clock in spi mode
Date: Wed, 18 Sep 2019 09:41:29 +0800	[thread overview]
Message-ID: <2a45205b-b9f1-b985-4a75-546b454c2e54@intel.com> (raw)
In-Reply-To: <4b015529-aeaa-b01f-01ce-1a81cbe2aea9@microchip.com>

Hi Adham,

On 9/17/19 9:03 AM, Adham.Abozaeid@microchip.com wrote:
>
> On 9/16/19 5:49 PM, kbuild test robot wrote:
>> [auto build test ERROR on linus/master]
>> [cannot apply to v5.3 next-20190916]
>> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
> This patch applies for staging-testing, not linus/master.
>
>

Thanks for clarification, we'll take a look. BTW 0day-CI introduced 
'--base' option to record base tree info in format-patch.
could you kindly add it to help robot to base on the right tree? please 
see https://stackoverflow.com/a/37406982

Best Regards,
Rong Chen

  reply	other threads:[~2019-09-18  1:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-16 19:37 [PATCH] staging: wilc1000: look for rtc_clk clock in spi mode Adham.Abozaeid
2019-09-17  0:49 ` kbuild test robot
2019-09-17  1:03   ` Adham.Abozaeid
2019-09-18  1:41     ` Rong Chen [this message]
2019-09-17  7:11 ` Claudiu.Beznea
2019-09-17  7:20   ` Claudiu.Beznea

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=2a45205b-b9f1-b985-4a75-546b454c2e54@intel.com \
    --to=rong.a.chen@intel.com \
    --cc=Adham.Abozaeid@microchip.com \
    --cc=Ajay.Kathat@microchip.com \
    --cc=Eugen.Hristev@microchip.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=johannes@sipsolutions.net \
    --cc=kbuild-all@01.org \
    --cc=linux-wireless@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