From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org, patches@lists.linux.dev
Subject: Re: [PATCH -next] pinctrl: qcom: Include bitfield.h in pinctrl-lpass-lpi.c
Date: Tue, 1 Nov 2022 17:02:45 +0200 [thread overview]
Message-ID: <Y2E1FbRvyN6myNR2@smile.fi.intel.com> (raw)
In-Reply-To: <Y1rcUbCVJi7QhcFK@smile.fi.intel.com>
On Thu, Oct 27, 2022 at 10:30:26PM +0300, Andy Shevchenko wrote:
> On Thu, Oct 27, 2022 at 12:16:25PM -0700, Nathan Chancellor wrote:
> > When building ARCH=arm allmodconfig, the following error occurs:
I have pushed my version to the tree, so it will appear in the next Linux Next.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2022-11-01 15:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 19:16 [PATCH -next] pinctrl: qcom: Include bitfield.h in pinctrl-lpass-lpi.c Nathan Chancellor
2022-10-27 19:30 ` Andy Shevchenko
2022-11-01 15:02 ` Andy Shevchenko [this message]
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=Y2E1FbRvyN6myNR2@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=patches@lists.linux.dev \
/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