From: Guenter Roeck <linux@roeck-us.net>
To: Naresh Solanki <naresh.solanki@9elements.com>,
Andrew Jeffery <andrew@codeconstruct.com.au>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
jdelvare@suse.com, sylv@sylv.io, linux-hwmon@vger.kernel.org,
Joel Stanley <joel@jms.id.au>,
Patrick Rudolph <patrick.rudolph@9elements.com>,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org
Subject: Re: [PATCH v6 2/2] ARM: dts: aspeed: sbp1: IBM sbp1 BMC board
Date: Tue, 5 Nov 2024 07:47:33 -0800 [thread overview]
Message-ID: <7d9657ff-1c4a-4167-982a-9f07e7b51f77@roeck-us.net> (raw)
In-Reply-To: <CABqG17j8RhFpNV+nJ=nLY8+uO_XXjbN55+Ce8op=6Dj5Z=_WOA@mail.gmail.com>
On 11/4/24 20:10, Naresh Solanki wrote:
[ ... ]
>> From a spot check, the warnings seem legitimate. Did you send the right
>> patches?
> Just checked again. They are resolved. But I guess the dtbinding patch
> for the above warning are merged in hwmon-next branch & not in dt/next
>
Did I apply some patches which should have been applied elsewhere ?
If so, please let me know, and I'll drop them.
Guenter
next prev parent reply other threads:[~2024-11-05 15:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 9:22 [PATCH v6 1/2] dt-bindings: arm: aspeed: add IBM SBP1 board Naresh Solanki
2024-11-04 14:39 ` Rob Herring (Arm)
2024-11-04 18:49 ` Conor Dooley
2024-11-05 0:09 ` Andrew Jeffery
2024-11-05 18:53 ` Conor Dooley
2024-11-05 23:34 ` Andrew Jeffery
[not found] ` <20241104092220.2268805-2-naresh.solanki@9elements.com>
2024-11-05 0:33 ` [PATCH v6 2/2] ARM: dts: aspeed: sbp1: IBM sbp1 BMC board Andrew Jeffery
2024-11-05 4:10 ` Naresh Solanki
2024-11-05 15:47 ` Guenter Roeck [this message]
2024-11-05 17:34 ` Naresh Solanki
2024-11-05 23:21 ` Andrew Jeffery
2024-11-06 0:37 ` [PATCH v6 1/2] dt-bindings: arm: aspeed: add IBM SBP1 board Andrew Jeffery
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=7d9657ff-1c4a-4167-982a-9f07e7b51f77@roeck-us.net \
--to=linux@roeck-us.net \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naresh.solanki@9elements.com \
--cc=patrick.rudolph@9elements.com \
--cc=robh@kernel.org \
--cc=sylv@sylv.io \
/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