linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Kever Yang <kever.yang@rock-chips.com>
Cc: "Jianqun Xu" <jay.xu@rock-chips.com>,
	"Heiko Stübner" <heiko@sntech.de>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	"open list:ARM/Rockchip SoC..."
	<linux-rockchip@lists.infradead.org>
Subject: Re: [PATCH] pinctrl: rockchip: make driver be tristate module【请注意,邮件由linux-rockchip-bounces+kever.yang=rock-chips.com@lists.infradead.org代发】
Date: Wed, 10 Mar 2021 14:47:10 +0100	[thread overview]
Message-ID: <CACRpkdb-NS5U3-nv6uRCsqo6iOg_CKq1tx8abNT4DuVpGPoqkw@mail.gmail.com> (raw)
In-Reply-To: <CAKUh=RxWDyW_cO2nKFLi=x0xDJwLHTb3+-OesTk2B5C=DpGEwg@mail.gmail.com>

On Fri, Mar 5, 2021 at 2:02 AM Kever Yang <kever.yang@rock-chips.com> wrote:

> Hi Linus,
>     Is there a place we can see the error report for "x86_64 allmodconfig"?
> Since we don't have a build environment for architectures other than arm,
> it would be best if we can get the error without have to setup the build environment.

It comes out from the kernel build robot when I apply the patch, hehe :D

But I think the kernel build robot people at Arm can pick any git branch
for builds, on request.

Yours,
Linus Walleij

      parent reply	other threads:[~2021-03-10 13:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23  6:42 [PATCH] pinctrl: rockchip: make driver be tristate module Jianqun Xu
2021-03-02 13:18 ` Linus Walleij
2021-03-04  8:18   ` Linus Walleij
     [not found]     ` <CAKUh=RxWDyW_cO2nKFLi=x0xDJwLHTb3+-OesTk2B5C=DpGEwg@mail.gmail.com>
2021-03-10 13:47       ` Linus Walleij [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=CACRpkdb-NS5U3-nv6uRCsqo6iOg_CKq1tx8abNT4DuVpGPoqkw@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=heiko@sntech.de \
    --cc=jay.xu@rock-chips.com \
    --cc=kever.yang@rock-chips.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    /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).