From: Quan Nguyen <quan@os.amperecomputing.com>
To: Rob Herring <robh@kernel.org>
Cc: Corey Minyard <minyard@acm.org>, Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@aj.id.au>, Wolfram Sang <wsa@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
openipmi-developer@lists.sourceforge.net,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux-i2c@vger.kernel.org, openbmc@lists.ozlabs.org,
Open Source Submission <patches@amperecomputing.com>,
Phong Vo <phong@os.amperecomputing.com>,
"Thang Q . Nguyen" <thang@os.amperecomputing.com>
Subject: Re: [PATCH v2 3/3] bindings: ipmi: Add binding for Aspeed SSIF BMC driver
Date: Fri, 2 Apr 2021 08:59:58 +0700 [thread overview]
Message-ID: <62acc395-de5b-fd5c-c74f-d7d713b43377@os.amperecomputing.com> (raw)
In-Reply-To: <20210401170933.GA622142@robh.at.kernel.org>
On 02/04/2021 00:09, Rob Herring wrote:
> On Tue, Mar 30, 2021 at 09:10:29PM +0700, Quan Nguyen wrote:
>> Add device tree binding document for the Aspeed SSIF BMC driver.
>>
>> Signed-off-by: Quan Nguyen <quan@os.amperecomputing.com>
>> ---
>> .../bindings/ipmi/aspeed-ssif-bmc.txt | 18 ++++++++++++++++++
>> 1 file changed, 18 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/ipmi/aspeed-ssif-bmc.txt
>
> Same comment as you ignored on v1.
>
Dear Rob,
I really did not mean to do that.
What happen is that there was a compilation error complaint by kernel
robot test on my v1. So I tried to send my v2 to fix that issue asap.
Unfortunately, your reply on my v1 arrived just right after I hit "git
send-email" to send out my v2.
For this comment, I'll switch to use yaml file in next version.
- Quan
WARNING: multiple messages have this Message-ID (diff)
From: Quan Nguyen <quan@os.amperecomputing.com>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, linux-aspeed@lists.ozlabs.org,
Corey Minyard <minyard@acm.org>, Andrew Jeffery <andrew@aj.id.au>,
openbmc@lists.ozlabs.org,
"Thang Q . Nguyen" <thang@os.amperecomputing.com>,
linux-kernel@vger.kernel.org,
Phong Vo <phong@os.amperecomputing.com>,
Wolfram Sang <wsa@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
openipmi-developer@lists.sourceforge.net,
Open Source Submission <patches@amperecomputing.com>,
linux-arm-kernel@lists.infradead.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH v2 3/3] bindings: ipmi: Add binding for Aspeed SSIF BMC driver
Date: Fri, 2 Apr 2021 08:59:58 +0700 [thread overview]
Message-ID: <62acc395-de5b-fd5c-c74f-d7d713b43377@os.amperecomputing.com> (raw)
In-Reply-To: <20210401170933.GA622142@robh.at.kernel.org>
On 02/04/2021 00:09, Rob Herring wrote:
> On Tue, Mar 30, 2021 at 09:10:29PM +0700, Quan Nguyen wrote:
>> Add device tree binding document for the Aspeed SSIF BMC driver.
>>
>> Signed-off-by: Quan Nguyen <quan@os.amperecomputing.com>
>> ---
>> .../bindings/ipmi/aspeed-ssif-bmc.txt | 18 ++++++++++++++++++
>> 1 file changed, 18 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/ipmi/aspeed-ssif-bmc.txt
>
> Same comment as you ignored on v1.
>
Dear Rob,
I really did not mean to do that.
What happen is that there was a compilation error complaint by kernel
robot test on my v1. So I tried to send my v2 to fix that issue asap.
Unfortunately, your reply on my v1 arrived just right after I hit "git
send-email" to send out my v2.
For this comment, I'll switch to use yaml file in next version.
- Quan
WARNING: multiple messages have this Message-ID (diff)
From: Quan Nguyen <quan@os.amperecomputing.com>
To: Rob Herring <robh@kernel.org>
Cc: Corey Minyard <minyard@acm.org>, Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@aj.id.au>, Wolfram Sang <wsa@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
openipmi-developer@lists.sourceforge.net,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux-i2c@vger.kernel.org, openbmc@lists.ozlabs.org,
Open Source Submission <patches@amperecomputing.com>,
Phong Vo <phong@os.amperecomputing.com>,
"Thang Q . Nguyen" <thang@os.amperecomputing.com>
Subject: Re: [PATCH v2 3/3] bindings: ipmi: Add binding for Aspeed SSIF BMC driver
Date: Fri, 2 Apr 2021 08:59:58 +0700 [thread overview]
Message-ID: <62acc395-de5b-fd5c-c74f-d7d713b43377@os.amperecomputing.com> (raw)
In-Reply-To: <20210401170933.GA622142@robh.at.kernel.org>
On 02/04/2021 00:09, Rob Herring wrote:
> On Tue, Mar 30, 2021 at 09:10:29PM +0700, Quan Nguyen wrote:
>> Add device tree binding document for the Aspeed SSIF BMC driver.
>>
>> Signed-off-by: Quan Nguyen <quan@os.amperecomputing.com>
>> ---
>> .../bindings/ipmi/aspeed-ssif-bmc.txt | 18 ++++++++++++++++++
>> 1 file changed, 18 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/ipmi/aspeed-ssif-bmc.txt
>
> Same comment as you ignored on v1.
>
Dear Rob,
I really did not mean to do that.
What happen is that there was a compilation error complaint by kernel
robot test on my v1. So I tried to send my v2 to fix that issue asap.
Unfortunately, your reply on my v1 arrived just right after I hit "git
send-email" to send out my v2.
For this comment, I'll switch to use yaml file in next version.
- Quan
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-04-02 2:00 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 14:10 [PATCH v2 0/3] Add Aspeed SSIF BMC driver Quan Nguyen
2021-03-30 14:10 ` Quan Nguyen
2021-03-30 14:10 ` Quan Nguyen
2021-03-30 14:10 ` [PATCH v2 1/3] i2c: i2c-core-smbus: Expose PEC calculate function for generic use Quan Nguyen
2021-03-30 14:10 ` Quan Nguyen
2021-03-30 14:10 ` Quan Nguyen
2021-03-30 14:10 ` [PATCH v2 2/3] drivers: char: ipmi: Add Aspeed SSIF BMC driver Quan Nguyen
2021-03-30 14:10 ` Quan Nguyen
2021-03-30 14:10 ` Quan Nguyen
2021-04-02 12:01 ` Philipp Zabel
2021-04-02 12:01 ` Philipp Zabel
2021-04-02 12:01 ` Philipp Zabel
2021-04-07 7:23 ` Quan Nguyen
2021-04-07 7:23 ` Quan Nguyen
2021-04-07 7:23 ` Quan Nguyen
2021-04-07 15:50 ` Corey Minyard
2021-04-07 15:50 ` Corey Minyard
2021-04-07 15:50 ` Corey Minyard
2021-04-22 10:49 ` Graeme Gregory
2021-04-22 10:49 ` Graeme Gregory
2021-04-22 10:49 ` Graeme Gregory
2021-03-30 14:10 ` [PATCH v2 3/3] bindings: ipmi: Add binding for " Quan Nguyen
2021-03-30 14:10 ` Quan Nguyen
2021-03-30 14:10 ` Quan Nguyen
2021-04-01 17:09 ` Rob Herring
2021-04-01 17:09 ` Rob Herring
2021-04-01 17:09 ` Rob Herring
2021-04-02 1:59 ` Quan Nguyen [this message]
2021-04-02 1:59 ` Quan Nguyen
2021-04-02 1:59 ` Quan Nguyen
2021-04-02 14:21 ` [PATCH v2 0/3] Add " Corey Minyard
2021-04-02 14:21 ` Corey Minyard
2021-04-02 14:21 ` Corey Minyard
2021-04-07 13:09 ` Quan Nguyen
2021-04-07 13:09 ` Quan Nguyen
2021-04-07 13:09 ` Quan Nguyen
2021-04-07 14:28 ` Corey Minyard
2021-04-07 14:28 ` Corey Minyard
2021-04-07 14:28 ` Corey Minyard
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=62acc395-de5b-fd5c-c74f-d7d713b43377@os.amperecomputing.com \
--to=quan@os.amperecomputing.com \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=openbmc@lists.ozlabs.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=p.zabel@pengutronix.de \
--cc=patches@amperecomputing.com \
--cc=phong@os.amperecomputing.com \
--cc=robh@kernel.org \
--cc=thang@os.amperecomputing.com \
--cc=wsa@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.