Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20220427104825.15a04680@canb.auug.org.au> <20220502121736.57b06150@canb.auug.org.au>
In-Reply-To: <20220502121736.57b06150@canb.auug.org.au>
From:   Dmitry Torokhov <dmitry.torokhov@gmail.com>
Date:   Thu, 5 May 2022 17:25:39 -0700
Message-ID: <CAKdAkRQN48WjsW1BAztTn3-c0pf68tP9+G0028ZyXB4-8aCtKQ@mail.gmail.com>
Subject: Re: linux-next: build failure after merge of the input tree
To:     Stephen Rothwell <sfr@canb.auug.org.au>
Cc:     Fabien Parent <fparent@baylibre.com>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Sun, May 1, 2022 at 7:17 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> On Wed, 27 Apr 2022 10:48:25 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > After merging the input tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > drivers/input/keyboard/mtk-pmic-keys.c:93:36: error: 'MT6359_TOPSTATUS' undeclared here (not in a function); did you mean 'MT6358_TOPSTATUS'?
> >    93 |                 MTK_PMIC_KEYS_REGS(MT6359_TOPSTATUS,
> >       |                                    ^~~~~~~~~~~~~~~~
> > drivers/input/keyboard/mtk-pmic-keys.c:48:35: note: in definition of macro 'MTK_PMIC_KEYS_REGS'
> >    48 |         .deb_reg                = _deb_reg,             \
> >       |                                   ^~~~~~~~
> > drivers/input/keyboard/mtk-pmic-keys.c:98:25: error: 'MT6359_TOP_RST_MISC' undeclared here (not in a function); did you mean 'MT6358_TOP_RST_MISC'?
> >    98 |         .pmic_rst_reg = MT6359_TOP_RST_MISC,
> >       |                         ^~~~~~~~~~~~~~~~~~~
> >       |                         MT6358_TOP_RST_MISC
> >
> > Caused by commit
> >
> >   0f97adf64314 ("Input: mtk-pmic-keys - add support for MT6359")
> >
> > I have used the input tree from next-20220426 for today.
>
> I am still getting this failure.

Sorry for sitting on this. I dropped the patches from my tree, we can
either push them through MFD, or retry after the merge window.

Thanks.

-- 
Dmitry