All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Thierry Reding" <thierry.reding@gmail.com>,
	arm@kernel.org, soc@kernel.org
Cc: "Jon Hunter" <jonathanh@nvidia.com>,
	linux-tegra@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 2/6] soc/tegra: cbb: Changes for v6.1-rc1
Date: Fri, 23 Sep 2022 18:13:06 +0200	[thread overview]
Message-ID: <758904b9-6b46-4e90-a4fd-b919a4dd0e95@www.fastmail.com> (raw)
In-Reply-To: <20220916101957.1635854-2-thierry.reding@gmail.com>

On Fri, Sep 16, 2022, at 12:19 PM, Thierry Reding wrote:
> Hi ARM SoC maintainers,
>
> The following changes since commit 568035b01cfb107af8d2e4bd2fb9aea22cf5b868:
>
>   Linux 6.0-rc1 (2022-08-14 15:50:18 -0700)
>
> are available in the Git repository at:
>
>   git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git 
> tags/tegra-for-6.1-cbb
>
> for you to fetch changes up to 53283105cab6f408968b7546826303ad329e9983:
>
>   soc/tegra: cbb: Add support for Tegra241 (Grace) (2022-09-15 12:41:36 +0200)
>
> I've split this out separately for now because after the discussion
> last release cycle there wasn't quite consensus about where this should
> go. The EDAC maintainers said that they didn't think it'd be a good fit
> so I'm including it again for ARM SoC here, but it being on a separate
> branch it won't block any of the other patches from going in if this is
> still a contentious topic.
>

Thank you for splitting it out. I'm not too happy about having
this driver in drivers/soc, as I still think it deserves to be in
a real subsystem with a generalized user interface.

I had hoped it would fit into EDAC, but I can understand that
this is not a great fit in the end. Since the driver has no
stable (ioctl or sysfs) interface but only a debugfs one that
can change at any time, my hope is that we can come up with
something better in the long run, e.g. when another SoC family
has a similar requirement and we create a more generic and
stable interface.

In the meantime, we can keep it in drivers/soc, so it's now
merged into the arm/drivers branch.

     Arnd

WARNING: multiple messages have this Message-ID (diff)
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Thierry Reding" <thierry.reding@gmail.com>,
	arm@kernel.org, soc@kernel.org
Cc: "Jon Hunter" <jonathanh@nvidia.com>,
	linux-tegra@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 2/6] soc/tegra: cbb: Changes for v6.1-rc1
Date: Fri, 23 Sep 2022 18:13:06 +0200	[thread overview]
Message-ID: <758904b9-6b46-4e90-a4fd-b919a4dd0e95@www.fastmail.com> (raw)
In-Reply-To: <20220916101957.1635854-2-thierry.reding@gmail.com>

On Fri, Sep 16, 2022, at 12:19 PM, Thierry Reding wrote:
> Hi ARM SoC maintainers,
>
> The following changes since commit 568035b01cfb107af8d2e4bd2fb9aea22cf5b868:
>
>   Linux 6.0-rc1 (2022-08-14 15:50:18 -0700)
>
> are available in the Git repository at:
>
>   git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git 
> tags/tegra-for-6.1-cbb
>
> for you to fetch changes up to 53283105cab6f408968b7546826303ad329e9983:
>
>   soc/tegra: cbb: Add support for Tegra241 (Grace) (2022-09-15 12:41:36 +0200)
>
> I've split this out separately for now because after the discussion
> last release cycle there wasn't quite consensus about where this should
> go. The EDAC maintainers said that they didn't think it'd be a good fit
> so I'm including it again for ARM SoC here, but it being on a separate
> branch it won't block any of the other patches from going in if this is
> still a contentious topic.
>

Thank you for splitting it out. I'm not too happy about having
this driver in drivers/soc, as I still think it deserves to be in
a real subsystem with a generalized user interface.

I had hoped it would fit into EDAC, but I can understand that
this is not a great fit in the end. Since the driver has no
stable (ioctl or sysfs) interface but only a debugfs one that
can change at any time, my hope is that we can come up with
something better in the long run, e.g. when another SoC family
has a similar requirement and we create a more generic and
stable interface.

In the meantime, we can keep it in drivers/soc, so it's now
merged into the arm/drivers branch.

     Arnd

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-09-23 16:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-16 10:19 [GIT PULL 1/6] soc/tegra: Changes for v6.1-rc1 Thierry Reding
2022-09-16 10:19 ` Thierry Reding
2022-09-16 10:19 ` [GIT PULL 2/6] soc/tegra: cbb: " Thierry Reding
2022-09-16 10:19   ` Thierry Reding
2022-09-23 16:13   ` Arnd Bergmann [this message]
2022-09-23 16:13     ` Arnd Bergmann
2022-09-16 10:19 ` [GIT PULL 3/6] firmware: tegra: " Thierry Reding
2022-09-16 10:19   ` Thierry Reding
2022-09-16 10:19 ` [GIT PULL 4/6] dt-bindings: " Thierry Reding
2022-09-16 10:19   ` Thierry Reding
2022-09-16 10:19 ` [GIT PULL 5/6] arm64: tegra: Device tree changes " Thierry Reding
2022-09-16 10:19   ` Thierry Reding
2022-09-16 10:19 ` [GIT PULL 6/6] arm64: tegra: Default configuration " Thierry Reding
2022-09-16 10:19   ` Thierry Reding
2022-09-19 12:45 ` [GIT PULL 1/6] soc/tegra: Changes " Thierry Reding
2022-09-19 12:45   ` Thierry Reding
2022-09-23 14:52 ` patchwork-bot+linux-soc
2022-09-23 16:20 ` patchwork-bot+linux-soc

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=758904b9-6b46-4e90-a4fd-b919a4dd0e95@www.fastmail.com \
    --to=arnd@arndb.de \
    --cc=arm@kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=soc@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.