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
Date: Wed, 18 May 2022 11:39:37 +0800 [thread overview]
Message-ID: <YoRqeYlk8vJaFKFS@google.com> (raw)
In-Reply-To: <b159beea-c7ab-b175-26c2-496f82443470@gmail.com>
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].
next prev parent reply other threads:[~2022-05-18 3:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 11:38 linux-next: build warning after merge of the chrome-platform tree Stephen Rothwell
2022-05-17 13:09 ` Muhammad Usama Anjum
2022-05-18 3:23 ` Bagas Sanjaya
2022-05-18 3:39 ` Tzung-Bi Shih [this message]
2022-05-18 4:24 ` Muhammad Usama Anjum
-- strict thread matches above, loose matches on Subject: below --
2024-06-03 3:25 Stephen Rothwell
2024-06-03 4:20 ` Tzung-Bi Shih
2021-08-23 5:21 Stephen Rothwell
2021-08-30 7:21 ` Stephen Rothwell
2021-08-31 0:17 ` Benson Leung
2021-08-31 0:32 ` Stephen Rothwell
2019-04-16 4:30 Stephen Rothwell
2019-04-16 9:09 ` Enric Balletbo i Serra
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=YoRqeYlk8vJaFKFS@google.com \
--to=tzungbi@kernel.org \
--cc=bagasdotme@gmail.com \
--cc=bleung@google.com \
--cc=dmitry.torokhov@gmail.com \
--cc=groeck@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=usama.anjum@collabora.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.