From: <Conor.Dooley@microchip.com>
To: <jassisinghbrar@gmail.com>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>
Cc: <Daire.McNamara@microchip.com>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-riscv@lists.infradead.org>
Subject: Re: [PATCH 0/3] MPFS mailbox fixes
Date: Tue, 23 Aug 2022 18:41:57 +0000 [thread overview]
Message-ID: <814208de-e3e4-852b-766d-14889a6c3c91@microchip.com> (raw)
In-Reply-To: <20220805125618.733628-1-conor.dooley@microchip.com>
On 05/08/2022 13:56, Conor Dooley wrote:
> Hey all,
>
> I spotted a couple of bugs in my mailbox driver while developing some
> new features. None of the features these bugs relate to were in use so
> they've gone unnoticed until now. The binding screwup is unfortunate
> and I don't really know how I misread the register map so badly.
>
> Jassi:
> Not sure if you prefer developers to add a CC: stable or not to patches
> so I have left them out, but I would like to see them backported.
Hey Jassi,
Have you just not had a chance to look at this yet, or are you waiting
for me to resend with the extra fixes tag applied?
Thanks,
Conor.
>
> Thanks,
> Conor.
>
> Conor Dooley (3):
> dt-bindings: mailbox: fix the mpfs' reg property
> mailbox: mpfs: fix handling of the reg property
> mailbox: mpfs: account for mbox offsets while sending
>
> .../mailbox/microchip,mpfs-mailbox.yaml | 15 ++++++++---
> drivers/mailbox/mailbox-mpfs.c | 25 +++++++++++--------
> 2 files changed, 25 insertions(+), 15 deletions(-)
>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: <Conor.Dooley@microchip.com>
To: <jassisinghbrar@gmail.com>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>
Cc: <Daire.McNamara@microchip.com>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-riscv@lists.infradead.org>
Subject: Re: [PATCH 0/3] MPFS mailbox fixes
Date: Tue, 23 Aug 2022 18:41:57 +0000 [thread overview]
Message-ID: <814208de-e3e4-852b-766d-14889a6c3c91@microchip.com> (raw)
In-Reply-To: <20220805125618.733628-1-conor.dooley@microchip.com>
On 05/08/2022 13:56, Conor Dooley wrote:
> Hey all,
>
> I spotted a couple of bugs in my mailbox driver while developing some
> new features. None of the features these bugs relate to were in use so
> they've gone unnoticed until now. The binding screwup is unfortunate
> and I don't really know how I misread the register map so badly.
>
> Jassi:
> Not sure if you prefer developers to add a CC: stable or not to patches
> so I have left them out, but I would like to see them backported.
Hey Jassi,
Have you just not had a chance to look at this yet, or are you waiting
for me to resend with the extra fixes tag applied?
Thanks,
Conor.
>
> Thanks,
> Conor.
>
> Conor Dooley (3):
> dt-bindings: mailbox: fix the mpfs' reg property
> mailbox: mpfs: fix handling of the reg property
> mailbox: mpfs: account for mbox offsets while sending
>
> .../mailbox/microchip,mpfs-mailbox.yaml | 15 ++++++++---
> drivers/mailbox/mailbox-mpfs.c | 25 +++++++++++--------
> 2 files changed, 25 insertions(+), 15 deletions(-)
>
next prev parent reply other threads:[~2022-08-23 18:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 12:56 [PATCH 0/3] MPFS mailbox fixes Conor Dooley
2022-08-05 12:56 ` Conor Dooley
2022-08-05 12:56 ` [PATCH 1/3] dt-bindings: mailbox: fix the mpfs' reg property Conor Dooley
2022-08-05 12:56 ` Conor Dooley
2022-08-05 13:01 ` Conor.Dooley
2022-08-05 13:01 ` Conor.Dooley
2022-08-08 7:01 ` Krzysztof Kozlowski
2022-08-08 7:01 ` Krzysztof Kozlowski
2022-08-05 12:56 ` [PATCH 2/3] mailbox: mpfs: fix handling of the " Conor Dooley
2022-08-05 12:56 ` Conor Dooley
2022-08-05 12:56 ` [PATCH 3/3] mailbox: mpfs: account for mbox offsets while sending Conor Dooley
2022-08-05 12:56 ` Conor Dooley
2022-08-23 18:41 ` Conor.Dooley [this message]
2022-08-23 18:41 ` [PATCH 0/3] MPFS mailbox fixes Conor.Dooley
2022-08-23 18:44 ` Jassi Brar
2022-08-23 18:44 ` Jassi Brar
2022-08-23 18:46 ` Conor.Dooley
2022-08-23 18:46 ` Conor.Dooley
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=814208de-e3e4-852b-766d-14889a6c3c91@microchip.com \
--to=conor.dooley@microchip.com \
--cc=Daire.McNamara@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=robh+dt@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.