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: <20210210091249.GC2774@vkoul-mobl.Dlink>
Date:   Wed, 10 Feb 2021 14:42:49 +0530
From:   Vinod Koul <vkoul@...nel.org>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     Kishon Vijay Abraham I <kishon@...com>,
        LKML <linux-kernel@...r.kernel.org>,
        linux-phy@...ts.infradead.org
Subject: Re: [GIT PULL] phy: second round of fixes for v5.11

On 09-02-21, 09:33, Greg KH wrote:
> On Fri, Feb 05, 2021 at 05:26:18PM +0530, Vinod Koul wrote:
> > Hello Greg,
> > 
> > Please pull to receive few phy driver fixes for v5.11.
> > Apologies for sending them bit late.
> > 
> > The following changes since commit d092bd9110494de3372722b317510b3692f1b2fe:
> > 
> >   phy: mediatek: allow compile-testing the dsi phy (2021-01-04 13:00:54 +0530)
> > 
> > are available in the Git repository at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/phy/linux-phy.git tags/phy-fixes2-5.11
> 
> It's too late for this for my tree, sorry.  Can you send these as
> patches and add a cc: stable on them to make sure they get into 5.11.y
> properly (and further back if they are needed)?

Ok I understand. But would it be okay to merge the fixes. Some folks
already use the tree and have requested the commits to be preserved.

I tested and it merges fine. I shall submit all these patches to stable
for 5.11 or earlier as applicable once they hit Linus's tree

Thanks
-- 
~Vinod

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ