From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-acpi@vger.kernel.org, linux-media@vger.kernel.org,
heikki.krogerus@linux.intel.com
Subject: Re: [PATCH v3 1/8] ACPI: property: Parse data node string references in properties
Date: Mon, 30 Jan 2023 23:34:53 +0200 [thread overview]
Message-ID: <Y9g3/fSDdBDVwQ+W@smile.fi.intel.com> (raw)
In-Reply-To: <CAJZ5v0g_KhDHRSOu_0tCtJPy9W1vMcXUF=qxc_6YJ=ADRNUv0g@mail.gmail.com>
On Mon, Jan 30, 2023 at 07:21:12PM +0100, Rafael J. Wysocki wrote:
> On Wed, Jan 25, 2023 at 11:41 PM Sakari Ailus
> <sakari.ailus@linux.intel.com> wrote:
> >
> > Add support for parsing property references using strings, besides
> > reference objects that were previously supported. This allows also
> > referencing data nodes which was not possible with reference objects.
> >
> > Also add pr_fmt() macro to prefix printouts.
> >
> > While at it, update copyright.
>
> While there is some design documentation in the last patch, at least
> some pieces of it should go into the changelog of this patch IMO.
>
> Also the spec-related information from the cover letter would be
> useful here, because cover letters don't go into the git record.
Interestingly if a maintainer starts using `b4` tool it has the mode in which
the series is represented as a pull request and cover letter contents go as a
commit message into the merge commit. That said, it depends on the maintainer's
workflow.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-01-30 21:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 22:40 [PATCH v3 0/8] ACPI _CRS CSI-2 and MIPI DisCo for Imaging support Sakari Ailus
2023-01-25 22:40 ` [PATCH v3 1/8] ACPI: property: Parse data node string references in properties Sakari Ailus
2023-01-27 9:57 ` Andy Shevchenko
2023-01-30 18:21 ` Rafael J. Wysocki
2023-01-30 21:34 ` Andy Shevchenko [this message]
2023-01-25 22:40 ` [PATCH v3 2/8] ACPI: property: Parse _CRS CSI-2 descriptor Sakari Ailus
2023-01-27 10:08 ` Andy Shevchenko
2023-01-30 21:18 ` Sakari Ailus
2023-01-30 21:37 ` Andy Shevchenko
2023-01-30 21:45 ` Sakari Ailus
2023-02-02 19:57 ` Rafael J. Wysocki
2023-02-02 20:57 ` Sakari Ailus
2023-01-25 22:40 ` [PATCH v3 3/8] device property: Add SOFTWARE_NODE() macro for defining software nodes Sakari Ailus
2023-01-25 22:40 ` [PATCH v3 4/8] ACPI: property: Generate camera swnodes for ACPI and DisCo for Imaging Sakari Ailus
2023-01-27 10:35 ` Andy Shevchenko
2023-01-27 10:35 ` Andy Shevchenko
2023-01-30 21:22 ` Sakari Ailus
2023-01-30 21:39 ` Andy Shevchenko
2023-01-30 21:46 ` Sakari Ailus
2023-01-25 22:40 ` [PATCH v3 5/8] ACPI: property: Dig "rotation" property for devices with CSI2 _CRS Sakari Ailus
2023-01-25 22:40 ` [PATCH v3 6/8] ACPI: property: Rename parsed MIPI DisCo for Imaging properties Sakari Ailus
2023-01-25 22:41 ` [PATCH v3 7/8] ACPI: property: Skip MIPI property table without "mipi-img" prefix Sakari Ailus
2023-01-25 22:41 ` [PATCH v3 8/8] ACPI: property: Document _CRS CSI-2 and DisCo for Imaging support Sakari Ailus
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=Y9g3/fSDdBDVwQ+W@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sakari.ailus@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 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.