From: Greg KH <greg@kroah.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: kbuild test robot <lkp@intel.com>,
Lee Jones <lee.jones@linaro.org>,
kbuild-all@01.org, Stephen Rothwell <sfr@canb.auug.org.au>,
Linus Walleij <linus.walleij@linaro.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Boris Brezillon <boris.brezillon@free-electrons.com>,
Alexander Stein <alexander.stein@systec-electronic.com>
Subject: Re: [PATCH] serial: st-asc: Use new GPIOD API to obtain RTS pin
Date: Wed, 8 Feb 2017 18:47:59 +0100 [thread overview]
Message-ID: <20170208174759.GA4773@kroah.com> (raw)
In-Reply-To: <1486571470.2133.404.camel@linux.intel.com>
On Wed, Feb 08, 2017 at 06:31:10PM +0200, Andy Shevchenko wrote:
> On Wed, 2017-02-08 at 21:48 +0800, kbuild test robot wrote:
> > Hi Lee,
> >
> > [auto build test ERROR on tty/tty-testing]
> > [cannot apply to v4.10-rc7 next-20170208]
> > [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/Lee-Jones/serial-st-a
> > sc-Use-new-GPIOD-API-to-obtain-RTS-pin/20170208-180609
> > base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git
> > tty-testing
> > config: x86_64-allmodconfig (attached as .config)
> > compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
> > reproduce:
> > # save the attached .config to linux build tree
> > make ARCH=x86_64
> >
>
> It requires to have immutable branch in one of the subsystem which the
> other one can pull.
Which sucks, and is why you should not do api changes this way!
greg k-h
next prev parent reply other threads:[~2017-02-08 17:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 5:11 linux-next: build failure after merge of the gpio tree Stephen Rothwell
2017-02-08 8:48 ` Lee Jones
2017-02-08 9:05 ` Boris Brezillon
2017-02-08 10:30 ` Stephen Rothwell
2017-02-08 9:24 ` [PATCH] serial: st-asc: Use new GPIOD API to obtain RTS pin Lee Jones
2017-02-08 13:00 ` Greg KH
2017-02-09 8:21 ` Lee Jones
2017-02-09 8:51 ` Greg KH
2017-02-13 9:59 ` Lee Jones
2017-02-21 10:26 ` Linus Walleij
2017-02-08 13:48 ` kbuild test robot
2017-02-08 16:31 ` Andy Shevchenko
2017-02-08 17:47 ` Greg KH [this message]
2017-02-08 19:42 ` Andy Shevchenko
2017-02-08 21:24 ` Stephen Rothwell
2017-02-13 15:18 ` linux-next: build failure after merge of the gpio tree 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=20170208174759.GA4773@kroah.com \
--to=greg@kroah.com \
--cc=alexander.stein@systec-electronic.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=boris.brezillon@free-electrons.com \
--cc=kbuild-all@01.org \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkp@intel.com \
--cc=sfr@canb.auug.org.au \
/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