From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Kartik <kkartik@nvidia.com>
Cc: thierry.reding@gmail.com, jonathanh@nvidia.com,
sumitg@nvidia.com, arnd@arndb.de, pshete@nvidia.com,
digetx@gmail.com, petlozup@nvidia.com, windhl@126.com,
frank.li@vivo.com, robh@kernel.org, stefank@nvidia.com,
pdeschrijver@nvidia.com, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/6] soc/tegra: fuse: Add ACPI support
Date: Wed, 6 Sep 2023 17:56:21 +0300 [thread overview]
Message-ID: <ZPiTFXa0/D2UN1SE@smile.fi.intel.com> (raw)
In-Reply-To: <20230905125824.2947-1-kkartik@nvidia.com>
On Tue, Sep 05, 2023 at 06:28:18PM +0530, Kartik wrote:
> This series of patches add ACPI support for Tegra194 and Tegra234 in
> Tegra fuse and apbmisc drivers. It also adds support for Tegra241
> which uses ACPI boot.
Neither here, nor in the individual patches I do _not_ see the changelog.
What's going on?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-09-06 14:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 12:58 [PATCH v2 0/6] soc/tegra: fuse: Add ACPI support Kartik
2023-09-05 12:58 ` [PATCH v2 1/6] soc/tegra: fuse: Refactor resource mapping Kartik
2023-09-05 12:58 ` [PATCH v2 2/6] soc/tegra: fuse: Add tegra_acpi_init_apbmisc() Kartik
2023-09-06 14:54 ` kernel test robot
2023-09-06 17:31 ` kernel test robot
2023-09-05 12:58 ` [PATCH v2 3/6] soc/tegra: fuse: Add function to add lookups Kartik
2023-09-05 12:58 ` [PATCH v2 4/6] soc/tegra: fuse: Add function to print SKU info Kartik
2023-09-05 12:58 ` [PATCH v2 5/6] soc/tegra: fuse: Add ACPI support for Tegra194 and Tegra234 Kartik
2023-09-05 12:58 ` [PATCH v2 6/6] soc/tegra: fuse: Add support for Tegra241 Kartik
2023-09-06 14:56 ` Andy Shevchenko [this message]
2023-09-07 7:11 ` [PATCH v2 0/6] soc/tegra: fuse: Add ACPI support Kartik
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=ZPiTFXa0/D2UN1SE@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=digetx@gmail.com \
--cc=frank.li@vivo.com \
--cc=jonathanh@nvidia.com \
--cc=kkartik@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=pdeschrijver@nvidia.com \
--cc=petlozup@nvidia.com \
--cc=pshete@nvidia.com \
--cc=robh@kernel.org \
--cc=stefank@nvidia.com \
--cc=sumitg@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=windhl@126.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.