linux-kernel - Re: [PATCH v2 0/3] drm/panel: mantix panel reset fixes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20201017104736.GA2822081@ravnborg.org>
Date:   Sat, 17 Oct 2020 12:47:36 +0200
From:   Sam Ravnborg <sam@...nborg.org>
To:     Guido Günther <agx@...xcpu.org>
Cc:     Thierry Reding <thierry.reding@...il.com>,
        David Airlie <airlied@...ux.ie>,
        Daniel Vetter <daniel@...ll.ch>,
        Rob Herring <robh+dt@...nel.org>,
        dri-devel@...ts.freedesktop.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/3] drm/panel: mantix panel reset fixes

Hi Guido.

On Sat, Oct 17, 2020 at 11:13:07AM +0200, Guido Günther wrote:
> Hi Sam,
> On Fri, Oct 16, 2020 at 04:29:16PM +0200, Sam Ravnborg wrote:
> > Hi Guido.
> > On Tue, Oct 13, 2020 at 12:32:45PM +0200, Guido Günther wrote:
> [..snip..]
> > > 
> > > Changes from v1:
> > >  - As per review comments by Fabio Estevam
> > >    https://lore.kernel.org/dri-devel/CAOMZO5B5ECcConvKej=RcaF8wvOxgq7nUzKJ-ad0aSAOzUqtbQ@mail.gmail.com/
> > >    - Fix typo in commit messages
> > >  - As per review comments by Rob Herring
> > >    https://lore.kernel.org/dri-devel/20200929174624.GA832332@bogus/
> > >    - Don't use an array of reset lines
> > > 
> > > Guido Günther (3):
> > >   drm/panel: mantix: Don't dereference NULL mode
> > >   drm/panel: mantix: Fix panel reset
> > >   dt-binding: display: Require two resets on mantix panel
> > 
> > All applied to drm-misc-next and pushed out.
> > And then I remembered you had commit right - sigh.
> 
> Thanks! Is there any special care needed to get that into 5.10? The
> driver landed there in 72967d5616d3f0c714f8eb6c4e258179a9031c45.

As the patches was applied to drm-misc-next the easiet path would
be to cherry-pick them and apply to drm-misc-fixes.
dim has cherry-pick support - try to use it rahter than doing it by
hand.

When you apply to drm-misc-fixes include a Fixes: tag so the tooling
will pick the patches automagically.

In hindsight the patches should have carried a Fixes: tag from a start
and should have been applied to drm-misc-fixes from a start too.

I have done something like above once or twice but anyway reach out if
you have questions. Or ask at #dri-devel.

	Sam