All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: "Csókás, Bence" <csokas.bence@prolan.hu>,
	"Sasha Levin" <sashal@kernel.org>
Subject: Re: [PATCH 6.11 v3 3/3] net: fec: make PPS channel configurable
Date: Mon,  2 Dec 2024 14:16:09 -0500	[thread overview]
Message-ID: <20241202125809-a4b6e45bc387a071@stable.kernel.org> (raw)
In-Reply-To: <20241202155713.3564460-4-csokas.bence@prolan.hu>

[ Sasha's backport helper bot ]

Hi,

Found matching upstream commit: 566c2d83887f0570056833102adc5b88e681b0c7

WARNING: Author mismatch between patch and found commit:
Backport author: =?UTF-8?q?Cs=C3=B3k=C3=A1s=2C=20Bence?= <csokas.bence@prolan.hu>
Commit author: Francesco Dolcini <francesco.dolcini@toradex.com>


Status in newer kernel trees:
6.12.y | Not found
6.11.y | Not found

Note: The patch differs from the upstream commit:
---
Failed to apply patch cleanly, falling back to interdiff...
---

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.11.y       |  Success    |  Success   |

WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: "Csókás, Bence" <csokas.bence@prolan.hu>,
	"Sasha Levin" <sashal@kernel.org>
Subject: Re: [PATCH 6.11 v3 3/3] net: fec: make PPS channel configurable
Date: Tue,  3 Dec 2024 13:13:29 -0500	[thread overview]
Message-ID: <20241202125809-a4b6e45bc387a071@stable.kernel.org> (raw)
Message-ID: <20241203181329.9AW1HdLHcj4Qf0NW7uuRjjf9eFXPZci93DWoM_A3Sos@z> (raw)
In-Reply-To: <20241202155713.3564460-4-csokas.bence@prolan.hu>

[ Sasha's backport helper bot ]

Hi,

Found matching upstream commit: 566c2d83887f0570056833102adc5b88e681b0c7

WARNING: Author mismatch between patch and found commit:
Backport author: =?UTF-8?q?Cs=C3=B3k=C3=A1s=2C=20Bence?= <csokas.bence@prolan.hu>
Commit author: Francesco Dolcini <francesco.dolcini@toradex.com>


Status in newer kernel trees:
6.12.y | Not found
6.11.y | Not found

Note: The patch differs from the upstream commit:
---
Failed to apply patch cleanly, falling back to interdiff...
---

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.11.y       |  Success    |  Success   |

  reply	other threads:[~2024-12-02 19:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-02 15:57 [PATCH 6.11 v3 0/3] Fix PPS channel routing Csókás, Bence
2024-12-02 15:57 ` [PATCH 6.11 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:10   ` Greg Kroah-Hartman
2024-12-02 15:57 ` [PATCH 6.11 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-03  9:10   ` Greg Kroah-Hartman
2024-12-02 15:57 ` [PATCH 6.11 v3 3/3] net: fec: make PPS channel configurable Csókás, Bence
2024-12-02 19:16   ` Sasha Levin [this message]
2024-12-03 18:13     ` Sasha Levin
2024-12-03  9:11   ` 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=20241202125809-a4b6e45bc387a071@stable.kernel.org \
    --to=sashal@kernel.org \
    --cc=csokas.bence@prolan.hu \
    --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.