From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Linux PCI <linux-pci@vger.kernel.org>
Subject: Re: [PATCH v6 0/7] resource: introduce union(), intersection() API
Date: Mon, 16 Nov 2020 17:59:40 +0100 [thread overview]
Message-ID: <CAJZ5v0hL2Pbus-U6i4nGaf1rwWNq6ZosVL6N2bwDiFw7W8tOEw@mail.gmail.com> (raw)
In-Reply-To: <20201116165159.GE4077@smile.fi.intel.com>
On Mon, Nov 16, 2020 at 5:51 PM Andy Shevchenko
<andriy.shevchenko@linux.intel.com> wrote:
>
> On Tue, Nov 03, 2020 at 10:45:03PM +0200, Andy Shevchenko wrote:
> > Some users may want to use resource library to manage their own resources,
> > besides existing users that open code union() and intersection()
> > implementations.
> >
> > Provide a generic API for wider use.
>
> Greg, Rafael, if there is no further comments, can it be applied?
I don't have any. so I can take this series if there are no concerns from Greg.
next prev parent reply other threads:[~2020-11-16 17:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 20:45 [PATCH v6 0/7] resource: introduce union(), intersection() API Andy Shevchenko
2020-11-03 20:45 ` [PATCH v6 3/7] resource: Introduce resource_union() for overlapping resources Andy Shevchenko
2020-11-03 20:45 ` [PATCH v6 6/7] PCI/ACPI: Replace open coded variant of resource_union() Andy Shevchenko
2020-11-16 16:51 ` [PATCH v6 0/7] resource: introduce union(), intersection() API Andy Shevchenko
2020-11-16 16:59 ` Rafael J. Wysocki [this message]
2020-11-17 17:08 ` Rafael J. Wysocki
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=CAJZ5v0hL2Pbus-U6i4nGaf1rwWNq6ZosVL6N2bwDiFw7W8tOEw@mail.gmail.com \
--to=rafael@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=sathyanarayanan.kuppuswamy@linux.intel.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;
as well as URLs for NNTP newsgroup(s).