Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19;
MIME-Version: 1.0
References: <CAPM=9tytg5jd_i3z3C5Y1dii2-cgO11Gjgvaq8qoWn3CGfCreg@mail.gmail.com>
 <CAL_JsqJqb6HYN5cw7GsyFobZxFmhU-ci8w4HKQEdFsx=bC_F3w@mail.gmail.com> <CAPM=9tx+YeOCBZ0WRcSMKTyUYr5ngySratZ0K8tmRZ0rCaFf8Q@mail.gmail.com>
In-Reply-To: <CAPM=9tx+YeOCBZ0WRcSMKTyUYr5ngySratZ0K8tmRZ0rCaFf8Q@mail.gmail.com>
From:   Rob Herring <robh@kernel.org>
Date:   Fri, 25 Mar 2022 15:04:43 -0500
Message-ID: <CAL_JsqJ7EN0_4qxZL55j2GOHc_D0zEeH1TS+Dp5WJA1bPdgwEQ@mail.gmail.com>
Subject: Re: [git pull] drm for 5.18-rc1
To:     Dave Airlie <airlied@gmail.com>
Cc:     Linus Torvalds <torvalds@linux-foundation.org>,
        Daniel Vetter <daniel.vetter@ffwll.ch>,
        LKML <linux-kernel@vger.kernel.org>,
        dri-devel <dri-devel@lists.freedesktop.org>,
        Chun-Kuang Hu <chunkuang.hu@kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Thu, Mar 24, 2022 at 10:01 PM Dave Airlie <airlied@gmail.com> wrote:
>
> > FYI, this breaks the DT bindings. The relevant patches didn't get
> > reviewed nor run thru automated testing because their encoding was
> > 'charset=y'[1]. (While email clients seem to just ignore that
> > encoding, patchwork and b4 do not.) linux-next is still broken and has
> > been since Mar 2[2]. v2 of the fixes[3] have been posted since Mar 9,
> > and still aren't in linux-next.
> >
> > It doesn't have to be fixed in this PR, but it needs to be fixed
> > before rc1. Otherwise, no one can test their bindings using rc1. In
> > general, there's no reason fixes need to wait until after rc1 as
> > Chun-Kuang suggests[4].
>
> With the conflicts that Linus merged, can we get this rebased onto
> Linus merge, and submitted to him?

I applied the series without issue on Linus' current tree aa5b537b0ecc
("Merge tag 'riscv-for-linus-5.18-mw0' of
git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux") and
confirmed the binding errors are fixed. Must be some difference in
what's in the Mediatek PR...

b4 shazam -lsSt 20220309134702.9942-1-jason-jh.lin@mediatek.com

Rob