linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Fabien Parent <fparent@baylibre.com>
Subject: Re: linux-next: build failure after merge of the input-current tree
Date: Thu, 23 May 2019 15:52:31 -0700	[thread overview]
Message-ID: <20190523225231.GD176265@dtor-ws> (raw)
In-Reply-To: <20190524082446.7d5bc21c@canb.auug.org.au>

On Fri, May 24, 2019 at 08:24:46AM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the input-current tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> drivers/input/keyboard/mtk-pmic-keys.c:21:10: fatal error: linux/mfd/mt6392/registers.h: No such file or directory
>  #include <linux/mfd/mt6392/registers.h>
>           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
> Caused by commit
> 
>   78094276ca6a ("Input: mtk-pmic-keys - add support for MT6392")
> 
> I have reverted that commit for today.

Sorry about that, I dropped the patch from the tree.

Thanks.

-- 
Dmitry

  reply	other threads:[~2019-05-23 22:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-23 22:24 linux-next: build failure after merge of the input-current tree Stephen Rothwell
2019-05-23 22:52 ` Dmitry Torokhov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-09-18 22:25 Stephen Rothwell
2018-09-18 22:32 ` Dmitry Torokhov
2018-09-20  8:02   ` Rafael J. Wysocki

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=20190523225231.GD176265@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=fparent@baylibre.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).