From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: [PATCH v1 0/2] Enable compile-testing for Tegra memory drivers
Date: Tue, 11 May 2021 00:37:27 +0300 [thread overview]
Message-ID: <20210510213729.7095-1-digetx@gmail.com> (raw)
Hi,
This small series enables compile-testing for all of NVIDIA Tegra memory
drivers.
Dmitry Osipenko (2):
soc/tegra: fuse: Add missing stubs
memory: tegra: Enable compile testing for all drivers
drivers/memory/tegra/Kconfig | 10 +++++-----
include/soc/tegra/fuse.h | 20 +++++++++++++++++---
2 files changed, 22 insertions(+), 8 deletions(-)
--
2.30.2
next reply other threads:[~2021-05-10 21:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 21:37 Dmitry Osipenko [this message]
2021-05-10 21:37 ` [PATCH v1 1/2] soc/tegra: fuse: Add missing stubs Dmitry Osipenko
2021-05-10 21:37 ` [PATCH v1 2/2] memory: tegra: Enable compile testing for all drivers Dmitry Osipenko
2021-05-11 13:58 ` kernel test robot
2021-05-11 13:58 ` kernel test robot
2021-05-11 15:17 ` Dmitry Osipenko
2021-05-11 15:17 ` Dmitry Osipenko
2021-05-11 15:31 ` Krzysztof Kozlowski
2021-05-11 15:31 ` Krzysztof Kozlowski
2021-05-11 16:00 ` Dmitry Osipenko
2021-05-11 16:00 ` Dmitry Osipenko
2021-05-11 17:35 ` Nathan Chancellor
2021-05-11 17:35 ` Nathan Chancellor
2021-05-11 17:57 ` Krzysztof Kozlowski
2021-05-11 17:57 ` Krzysztof Kozlowski
2021-05-11 18:36 ` Dmitry Osipenko
2021-05-11 18:36 ` Dmitry Osipenko
2021-05-11 15:43 ` kernel test robot
2021-05-11 15:43 ` kernel test robot
2021-05-11 16:22 ` Dmitry Osipenko
2021-05-11 16:22 ` Dmitry Osipenko
2021-05-11 16:41 ` Krzysztof Kozlowski
2021-05-11 18:30 ` Dmitry Osipenko
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=20210510213729.7095-1-digetx@gmail.com \
--to=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.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.