public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Saravana Kannan <saravanak@google.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Len Brown <lenb@kernel.org>
Subject: Re: [PATCH v1 1/1] device property: Add missed header in fwnode.h
Date: Wed, 13 Oct 2021 20:18:50 +0200	[thread overview]
Message-ID: <YWcjCmYnULuf1CsL@kroah.com> (raw)
In-Reply-To: <CAGETcx-Yaof2EFzY6C9JHjqi48UBg-nR7aACJ5nJa1T-rbv3Uw@mail.gmail.com>

On Wed, Oct 13, 2021 at 10:34:54AM -0700, Saravana Kannan wrote:
> On Wed, Oct 13, 2021 at 10:31 AM Rafael J. Wysocki <rafael@kernel.org> wrote:
> >
> > On Wed, Oct 13, 2021 at 7:21 PM Saravana Kannan <saravanak@google.com> wrote:
> > >
> > > On Wed, Oct 13, 2021 at 7:37 AM Andy Shevchenko
> > > <andriy.shevchenko@linux.intel.com> wrote:
> > > >
> > > > When adding some stuff to the header file we must not rely on
> > > > implicit dependencies that are happen by luck or bugs in other
> > > > headers. Hence fwnode.h needs to use bits.h directly.
> > > >
> > > > Fixes: c2c724c868c4 ("driver core: Add fw_devlink_parse_fwtree()")
> > > > Cc: Saravana Kannan <saravanak@google.com>
> > > > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > >
> > > Acked-by: Saravana Kannan <saravanak@google.com>
> >
> > I'm going to pick this up, thanks!
> >
> 
> I think Greg already picked it up.

I did, but multiple people can :)

thanks,

greg k-h

      reply	other threads:[~2021-10-13 18:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-13 14:37 [PATCH v1 1/1] device property: Add missed header in fwnode.h Andy Shevchenko
2021-10-13 17:21 ` Saravana Kannan
2021-10-13 17:30   ` Rafael J. Wysocki
2021-10-13 17:34     ` Saravana Kannan
2021-10-13 18:18       ` Greg Kroah-Hartman [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=YWcjCmYnULuf1CsL@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=saravanak@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox