From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Linux pin control <linux-gpio@vger.kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [GIT PULL] intel-pinctrl for 5.6-1
Date: Fri, 24 Jan 2020 15:21:37 +0200 [thread overview]
Message-ID: <20200124132137.GG32742@smile.fi.intel.com> (raw)
In-Reply-To: <CACRpkdba9zw3qN5MEVsRhdkebVfi-fHoiNU+FhCZfpoZ1g3vLw@mail.gmail.com>
On Fri, Jan 24, 2020 at 02:02:56PM +0100, Linus Walleij wrote:
> On Fri, Jan 24, 2020 at 11:57 AM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> > On Thu, Jan 23, 2020 at 03:45:14PM +0100, Linus Walleij wrote:
>
> > > Pulled this into my "devel" branch for v5.6.
> >
> > Thanks!
> > How long usually does it take to see in linux-next?
>
> What I need before I put it for-next is successful builds on a few
> archs.
>
> Zeroday has been smacky before so I could quickly cornfirm the branches
> build fine and that made things quicker in the past. But as of lately
> zeroday comes and goes a bit sporadically.
>
> I can do local builds of some archs but my computer isn't the most
> fantastic workhorse really.
>
> Lately I am investigating a cloud build service, it is quite promising,
> you see the branch "testmerge" in linux-gpio where I merge all
> the new stuff for GPIO and pin control and toss at the build server,
> so I am working on something here.
>
> Sometimes I just give up trying to build all stuff and submit it for
> next anyway but I'd rather not have to do that, it usually results
> in a patch storm of 4 different people fixing the same trivial
> issue in linux-next...
Thank you for so detailed answer! I didn't mean to complain or so,
I was just wondering...
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-01-24 13:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 10:09 [GIT PULL] intel-pinctrl for 5.6-1 Andy Shevchenko
2020-01-23 14:45 ` Linus Walleij
2020-01-24 10:57 ` Andy Shevchenko
2020-01-24 13:02 ` Linus Walleij
2020-01-24 13:21 ` Andy Shevchenko [this message]
2020-01-24 13:33 ` Linus Walleij
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=20200124132137.GG32742@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mika.westerberg@linux.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 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.