From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Csókás, Bence" <csokas.bence@prolan.hu>
Cc: stable@vger.kernel.org,
Francesco Dolcini <francesco.dolcini@toradex.com>,
Frank Li <Frank.Li@nxp.com>, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH 6.6 3/3] net: fec: refactor PPS channel configuration
Date: Fri, 18 Oct 2024 12:37:37 +0200 [thread overview]
Message-ID: <2024101822-calamari-litigate-8d87@gregkh> (raw)
In-Reply-To: <20241016080156.265251-3-csokas.bence@prolan.hu>
On Wed, Oct 16, 2024 at 10:01:57AM +0200, Csókás, Bence wrote:
> From: Francesco Dolcini <francesco.dolcini@toradex.com>
>
> Preparation patch to allow for PPS channel configuration, no functional
> change intended.
>
> Signed-off-by: Francesco Dolcini <francesco.dolcini@toradex.com>
> Reviewed-by: Frank Li <Frank.Li@nxp.com>
> Reviewed-by: Csókás, Bence <csokas.bence@prolan.hu>
> Signed-off-by: Paolo Abeni <pabeni@redhat.com>
>
> (cherry picked from commit bf8ca67e21671e7a56e31da45360480b28f185f1)
Not a valid commit id in Linus's tree :(
next prev parent reply other threads:[~2024-10-18 10:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 6:41 [REQUEST] net: fec: Not yet ported PTP patches Csókás Bence
2024-10-16 8:01 ` [PATCH 6.6 1/3] net: fec: Move `fec_ptp_read()` to the top of the file Csókás, Bence
2024-11-22 13:51 ` Sasha Levin
2024-11-22 13:56 ` Csókás Bence
2024-11-23 14:36 ` Sasha Levin
2024-11-24 10:47 ` Csókás Bence
2024-11-24 12:06 ` Sasha Levin
2024-10-16 8:01 ` [PATCH 6.6 2/3] net: fec: Remove duplicated code Csókás, Bence
2024-10-16 8:01 ` [PATCH 6.6 3/3] net: fec: refactor PPS channel configuration Csókás, Bence
2024-10-18 10:37 ` Greg Kroah-Hartman [this message]
2024-11-22 9:10 ` Csókás Bence
2024-11-22 11:04 ` Greg Kroah-Hartman
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=2024101822-calamari-litigate-8d87@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Frank.Li@nxp.com \
--cc=csokas.bence@prolan.hu \
--cc=francesco.dolcini@toradex.com \
--cc=pabeni@redhat.com \
--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 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.