From: Aswath Govindraju <a-govindraju@ti.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Swapnil Jakhade <sjakhade@cadence.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
<linux-phy@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] phy: cadence: Sierra: Add support for skipping configuration
Date: Thu, 3 Feb 2022 11:25:29 +0530 [thread overview]
Message-ID: <3444e347-2603-6f5b-94de-09642c41fc27@ti.com> (raw)
In-Reply-To: <YfseaJADVocxqnOu@matsya>
Hi Vinod,
On 03/02/22 5:44 am, Vinod Koul wrote:
> On 02-02-22, 20:14, Aswath Govindraju wrote:
>> Hi Vinod,
>>
>> On 02/02/22 7:53 pm, Vinod Koul wrote:
>>> On 28-01-22, 12:56, Aswath Govindraju wrote:
>>>> In some cases, a single SerDes instance can be shared between two different
>>>> processors, each using a separate link. In these cases, the SerDes
>>>> configuration is done in an earlier boot stage. Therefore, add support to
>>>> skip reconfiguring, if it is was already configured beforehand.
>>>
>>> This fails to apply, pls rebase and resend
>>>
>>
>> On rebasing, I am seeing no difference in the patch and I am able to
>> apply it on top of linux-next/master commit 6abab1b81b65. May I know if
>> there is any other branch that I would need to rebase this patch on top of?
>
> It should be based on phy-next which is at
> 1f1b0c105b19ac0d90975e2569040da1216489b7 now
>
I have posted a respin of this patch after rebasing it on top of
phy-next. One aspect that is not clear to me is, phy-next branch does
not have the following commit which is present in linux-next master,
29afbd769ca3 phy: cadence: Sierra: fix error handling bugs in probe()
When the respin of this patch(v3) is merged with linux-next/master
wouldn't it cause merge-conflicts?
May I know how would this be handled?
Link to v3:
- https://patchwork.kernel.org/project/linux-phy/list/?series=610903
Thanks,
Aswath
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2022-02-03 5:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 7:26 [PATCH v2] phy: cadence: Sierra: Add support for skipping configuration Aswath Govindraju
2022-01-28 7:38 ` Dan Carpenter
2022-02-02 4:55 ` Vinod Koul
2022-02-02 5:31 ` Aswath Govindraju
2022-02-02 14:23 ` Vinod Koul
2022-02-02 14:44 ` Aswath Govindraju
2022-02-03 0:14 ` Vinod Koul
2022-02-03 5:55 ` Aswath Govindraju [this message]
2022-02-04 6:14 ` Vinod Koul
2022-02-04 6:18 ` Aswath Govindraju
2022-02-07 4:58 ` Vinod Koul
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=3444e347-2603-6f5b-94de-09642c41fc27@ti.com \
--to=a-govindraju@ti.com \
--cc=dan.carpenter@oracle.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=p.zabel@pengutronix.de \
--cc=sjakhade@cadence.com \
--cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).