Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
Date:   Wed, 18 May 2022 11:39:37 +0800
From:   Tzung-Bi Shih <tzungbi@kernel.org>
To:     Bagas Sanjaya <bagasdotme@gmail.com>
Cc:     Muhammad Usama Anjum <usama.anjum@collabora.com>,
        Stephen Rothwell <sfr@canb.auug.org.au>,
        Benson Leung <bleung@google.com>,
        Guenter Roeck <groeck@chromium.org>,
        Dmitry Torokhov <dmitry.torokhov@gmail.com>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the chrome-platform tree
Message-ID: <YoRqeYlk8vJaFKFS@google.com>
References: <20220516213832.19127535@canb.auug.org.au>
 <5d148732-c14d-4e96-f8fc-31acc8932534@collabora.com>
 <b159beea-c7ab-b175-26c2-496f82443470@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <b159beea-c7ab-b175-26c2-496f82443470@gmail.com>
Precedence: bulk

On Wed, May 18, 2022 at 10:23:28AM +0700, Bagas Sanjaya wrote:
> On 5/17/22 20:09, Muhammad Usama Anjum wrote:
> > I've found these warnings in local build. But I'm unable to fix them.
> > Apparently, there doesn't seem any unexpected indentation. This kind of
> > same warnings have also appeared on some more files before this commit
> > without any reason.
> > 
> 
> Hi,
> 
> I've figured out the fix on [1]. Please review.
> 
> [1]: https://lore.kernel.org/linux-next/20220518031750.21923-2-bagasdotme@gmail.com/

Thanks for figuring it out.  I was also investigating on the issue but got no clues.

Reviewed on [1].