From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: bingbu.cao@intel.com
Cc: linux-media@vger.kernel.org, sakari.ailus@linux.intel.com,
hdegoede@redhat.com
Subject: Re: [PATCH] media: ipu-bridge: add mod_devicetable.h header inclusion
Date: Fri, 10 May 2024 18:07:00 +0300 [thread overview]
Message-ID: <Zj44FJHP5qUcaLmY@smile.fi.intel.com> (raw)
In-Reply-To: <20240510062747.3422256-1-bingbu.cao@intel.com>
On Fri, May 10, 2024 at 02:27:47PM +0800, bingbu.cao@intel.com wrote:
> From: Bingbu Cao <bingbu.cao@intel.com>
>
> ACPI_ID_LEN is defined in mod_devicetable.h, so the header should
> be guaranteed to included in ipu-bridge.h instead of the source
> files which include ipu-bridge.h.
Right,
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2024-05-10 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 6:27 [PATCH] media: ipu-bridge: add mod_devicetable.h header inclusion bingbu.cao
2024-05-10 15:07 ` 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=Zj44FJHP5qUcaLmY@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bingbu.cao@intel.com \
--cc=hdegoede@redhat.com \
--cc=linux-media@vger.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).