From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v2 1/2] ACPI: bus: Constify stubs for CONFIG_ACPI=n case
Date: Fri, 4 Jun 2021 19:48:53 +0300 [thread overview]
Message-ID: <YLpZdRKsj4UZbfgN@smile.fi.intel.com> (raw)
In-Reply-To: <20210604163433.12707-1-andriy.shevchenko@linux.intel.com>
On Fri, Jun 04, 2021 at 07:34:32PM +0300, Andy Shevchenko wrote:
> There is a few stubs that left untouched during constification of
> the fwnode related APIs. Constify three more stubs here.
Kbuild bot found another non-const APIs in use which requires an additional
change. I'll send v3 soon. Please, ignore this one.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2021-06-04 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 16:34 [PATCH v2 1/2] ACPI: bus: Constify stubs for CONFIG_ACPI=n case Andy Shevchenko
2021-06-04 16:34 ` [PATCH v2 2/2] device property: Unify access to of_node Andy Shevchenko
2021-06-04 16:48 ` 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=YLpZdRKsj4UZbfgN@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
/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).