All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>
Cc: <johannes@sipsolutions.net>, <linux-wireless@vger.kernel.org>,
	"Avinash Patil" <avinashp@quantenna.com>,
	Dmitrii Lebed <dlebed@quantenna.com>,
	"Sergei Maksimenko" <smaksimenko@quantenna.com>,
	Sergey Matyukevich <smatyukevich@quantenna.com>,
	Bindu Therthala <btherthala@quantenna.com>,
	Huizhao Wang <hwang@quantenna.com>,
	Kamlesh Rath <krath@quantenna.com>
Subject: Re: [v2, RESEND] qtnfmac: announcement of new FullMAC driver for Quantenna chipsets
Date: Tue, 26 Jul 2016 18:15:58 +0300	[thread overview]
Message-ID: <87h9bcctw1.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <c9a9f9f2-2943-14d2-3b5d-c401e870d7a0@quantenna.com> (Igor Mitsyanko's message of "Thu, 21 Jul 2016 10:26:39 -0700")

Igor Mitsyanko <igor.mitsyanko.os@quantenna.com> writes:

>     I applied this to the pending branch so that kbuild bot can run build tests on
>     it. Let's see what it finds.
>
>
>
> Kalle, I think you did that before already, at least I have received a
> following error report a while back:
>
>
> Hi,
>
> [auto build test ERROR on wireless-drivers-next/master]
> [also build test ERROR on v4.7-rc4 next-20160620]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
>
> url:    https://github.com/0day-ci/linux/commits/igor-mitsyanko-os-quantenna-com/qtnfmac-announcement-of-new-FullMAC-driver-for-Quantenna-chipsets/20160621-061419
> base:   https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next.git master
> config: m32r-allyesconfig (attached as .config)
> compiler: m32r-linux-gcc (GCC) 4.9.0
> reproduce:
>         wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         # save the attached .config to linux build tree
>         make.cross ARCH=m32r

I suspect that in this case the kbuild bot took the patch from the
mailing list and run some quick tests on that. But AFAIK commits on a
git tree get wider testing.

-- 
Kalle Valo

       reply	other threads:[~2016-07-26 15:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20160719073947.2345561267@smtp.codeaurora.org>
     [not found] ` <c9a9f9f2-2943-14d2-3b5d-c401e870d7a0@quantenna.com>
2016-07-26 15:15   ` Kalle Valo [this message]
2016-06-20 22:11 [PATCH v2 RESEND] qtnfmac: announcement of new FullMAC driver for Quantenna chipsets igor.mitsyanko.os
2016-07-19  7:39 ` [v2, " Kalle Valo

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=87h9bcctw1.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=avinashp@quantenna.com \
    --cc=btherthala@quantenna.com \
    --cc=dlebed@quantenna.com \
    --cc=hwang@quantenna.com \
    --cc=igor.mitsyanko.os@quantenna.com \
    --cc=johannes@sipsolutions.net \
    --cc=krath@quantenna.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=smaksimenko@quantenna.com \
    --cc=smatyukevich@quantenna.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.