From: Lee Jones <lee.jones@linaro.org>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: matthias.bgg@kernel.org, Rob Herring <robh@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH] dt-bindings: mfd: mediatek: Add MT6397 Pin Controller
Date: Fri, 22 May 2020 08:37:22 +0100 [thread overview]
Message-ID: <20200522073722.GP271301@dell> (raw)
In-Reply-To: <ce3747e5-41db-a168-0602-37337d8530f2@gmail.com>
On Thu, 21 May 2020, Matthias Brugger wrote:
> Hi Lee,
>
> On 15/01/2020 16:19, Rob Herring wrote:
> > On Fri, 10 Jan 2020 15:59:51 +0100, matthias.bgg@kernel.org wrote:
> >> From: Matthias Brugger <matthias.bgg@gmail.com>
> >>
> >> The MT6397 mfd includes a pin controller. Add binding
> >> a description for it.
> >>
> >> Signed-off-by: Matthias Brugger <matthias.bgg@gmail.com>
> >>
> >> ---
> >>
> >> Documentation/devicetree/bindings/mfd/mt6397.txt | 5 +++++
> >> 1 file changed, 5 insertions(+)
> >>
> >
> > Acked-by: Rob Herring <robh@kernel.org>
> >
>
> It looks like this fall through the cracks.
> Would you consider to queue it or do you have further comments?
There is a current issue where Rob and I are both taking patches.
Sometimes we both assume the other will take the patch.
Apologies.
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2020-05-22 7:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 14:59 [PATCH] dt-bindings: mfd: mediatek: Add MT6397 Pin Controller matthias.bgg
2020-01-13 7:08 ` Nicolas Boichat
2020-01-15 15:19 ` Rob Herring
2020-05-21 10:16 ` Matthias Brugger
2020-05-22 7:37 ` Lee Jones [this message]
2020-05-22 7:37 ` Lee Jones
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=20200522073722.GP271301@dell \
--to=lee.jones@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=matthias.bgg@kernel.org \
--cc=robh@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).