From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Csókás, Bence" <csokas.bence@prolan.hu>
Cc: stable@vger.kernel.org, Sasha Levin <sashal@kernel.org>,
Francesco Dolcini <francesco.dolcini@toradex.com>
Subject: Re: [PATCH 6.12 v3 0/3] Fix PPS channel routing
Date: Tue, 3 Dec 2024 10:10:18 +0100 [thread overview]
Message-ID: <2024120332-synergy-quadrant-574b@gregkh> (raw)
In-Reply-To: <20241202155800.3564611-1-csokas.bence@prolan.hu>
On Mon, Dec 02, 2024 at 04:57:57PM +0100, Csókás, Bence wrote:
> On certain i.MX8 series parts [1], the PPS channel 0
> is routed internally to eDMA, and the external PPS
> pin is available on channel 1. In addition, on
> certain boards, the PPS may be wired on the PCB to
> an EVENTOUTn pin other than 0. On these systems
> it is necessary that the PPS channel be able
> to be configured from the Device Tree.
>
> [1] https://lore.kernel.org/all/ZrPYOWA3FESx197L@lizhi-Precision-Tower-5810/
>
> Changes in v2:
> * add upstream hash (pick -x)
> Changes in v3:
> * Add S-o-b despite Sasha's complaining bot
Are you sure? I don't see them here. Please fix up.
And Sasha's bot is correct for this, it's just a warning that we need to
verify the patch a lot more stricter than if the original author were
sending this to us.
thanks,
greg k-h
prev parent reply other threads:[~2024-12-03 9:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 15:57 [PATCH 6.12 v3 0/3] Fix PPS channel routing Csókás, Bence
2024-12-02 15:57 ` [PATCH 6.12 v3 1/3] dt-bindings: net: fec: add pps channel property Csókás, Bence
2024-12-02 19:16 ` Sasha Levin
2024-12-03 18:13 ` Sasha Levin
2024-12-03 9:09 ` Greg Kroah-Hartman
2024-12-02 15:57 ` [PATCH 6.12 v3 2/3] net: fec: refactor PPS channel configuration Csókás, Bence
2024-12-02 19:16 ` Sasha Levin
2024-12-03 18:13 ` Sasha Levin
2024-12-02 15:58 ` [PATCH 6.12 v3 3/3] net: fec: make PPS channel configurable Csókás, Bence
2024-12-02 19:16 ` Sasha Levin
2024-12-03 18:13 ` Sasha Levin
2024-12-03 9:10 ` Greg Kroah-Hartman [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=2024120332-synergy-quadrant-574b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=csokas.bence@prolan.hu \
--cc=francesco.dolcini@toradex.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/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