From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH v1] ARM: dts: aspeed: yosemite4: Add i2c-mux for CPLD IOE on Spider Board
Date: Mon, 30 Sep 2024 15:32:01 +0930 [thread overview]
Message-ID: <81b9916f299bbf29583aba610c0147c8b8afd092.camel@codeconstruct.com.au> (raw)
In-Reply-To: <TYZPR04MB5853D743126A23AD41BE3E0DD6762@TYZPR04MB5853.apcprd04.prod.outlook.com>
On Mon, 2024-09-30 at 05:55 +0000, Delphine_CC_Chiu/WYHQ/Wiwynn wrote:
>
> I have one more question that if I need to add the DTS based on the patches that
> have been applied but haven't been merged in torvalds/linux.
> Should I also based on the branch "for/bmc/dt" from amboar/linux to create the
> patch?
>
You can do that, yes. We can at least then be sure your work won't
generate conflicts when I try to apply it (unless you've
inappropriately split your series).
Cheers,
Andrew
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Delphine_CC_Chiu/WYHQ/Wiwynn <Delphine_CC_Chiu@wiwynn.com>,
Patrick Williams <patrick@stwcx.xyz>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
Ricky CX Wu <ricky.cx.wu.wiwynn@gmail.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] ARM: dts: aspeed: yosemite4: Add i2c-mux for CPLD IOE on Spider Board
Date: Mon, 30 Sep 2024 15:32:01 +0930 [thread overview]
Message-ID: <81b9916f299bbf29583aba610c0147c8b8afd092.camel@codeconstruct.com.au> (raw)
In-Reply-To: <TYZPR04MB5853D743126A23AD41BE3E0DD6762@TYZPR04MB5853.apcprd04.prod.outlook.com>
On Mon, 2024-09-30 at 05:55 +0000, Delphine_CC_Chiu/WYHQ/Wiwynn wrote:
>
> I have one more question that if I need to add the DTS based on the patches that
> have been applied but haven't been merged in torvalds/linux.
> Should I also based on the branch "for/bmc/dt" from amboar/linux to create the
> patch?
>
You can do that, yes. We can at least then be sure your work won't
generate conflicts when I try to apply it (unless you've
inappropriately split your series).
Cheers,
Andrew
next prev parent reply other threads:[~2024-09-30 6:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 2:41 [PATCH v1] ARM: dts: aspeed: yosemite4: Add i2c-mux for CPLD IOE on Spider Board Delphine CC Chiu
2024-09-26 2:41 ` Delphine CC Chiu
2024-09-27 5:57 ` Andrew Jeffery
2024-09-27 5:57 ` Andrew Jeffery
2024-09-27 9:24 ` Delphine_CC_Chiu/WYHQ/Wiwynn
2024-09-27 9:24 ` Delphine_CC_Chiu/WYHQ/Wiwynn
2024-09-28 2:33 ` Patrick Williams
2024-09-28 2:33 ` Patrick Williams
2024-09-29 23:44 ` Andrew Jeffery
2024-09-29 23:44 ` Andrew Jeffery
2024-09-30 1:47 ` Delphine_CC_Chiu/WYHQ/Wiwynn
2024-09-30 1:47 ` Delphine_CC_Chiu/WYHQ/Wiwynn
2024-09-30 2:36 ` Andrew Jeffery
2024-09-30 2:36 ` Andrew Jeffery
2024-09-30 5:55 ` Delphine_CC_Chiu/WYHQ/Wiwynn
2024-09-30 5:55 ` Delphine_CC_Chiu/WYHQ/Wiwynn
2024-09-30 6:02 ` Andrew Jeffery [this message]
2024-09-30 6:02 ` Andrew Jeffery
2024-09-30 6:08 ` Delphine_CC_Chiu/WYHQ/Wiwynn
2024-09-30 6:08 ` Delphine_CC_Chiu/WYHQ/Wiwynn
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=81b9916f299bbf29583aba610c0147c8b8afd092.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=linux-aspeed@lists.ozlabs.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.