On Fri, Sep 30, 2022 at 1:56 PM Jerry Snitselaar <jsnitsel@xxxxxxxxxx> wrote: > > On Fri, Sep 30, 2022 at 12:44:22PM +0800, Koba Ko wrote: > > On Fri, Sep 30, 2022 at 1:26 AM Jerry Snitselaar <jsnitsel@xxxxxxxxxx> wrote: > > > > > > On Thu, 2022-09-29 at 22:40 +0530, Vinod Koul wrote: > > > > On 29-09-22, 09:57, Jerry Snitselaar wrote: > > > > > On Tue, Aug 30, 2022 at 05:32:07PM +0800, Koba Ko wrote: > > > > > > > > > > > > > > Hi Vinod, > > > > > > > > > > Any thoughts on this patch? We recently came across this issue as > > > > > well. > > > > > > > > I have only patch 3, where is the rest of the series... ? > > > > > > > > > > I never found anything else when I looked at this earlier. > > > The one thing I can think of is perhaps Koba was seeing multiple > > > issues at time when he found this, like: > > > > > > https://lore.kernel.org/linux-crypto/20220901144712.1192698-1-koba.ko@xxxxxxxxxxxxx/ > > > > > > That was also being seen by an engineer here that was looking > > > at client_count code. > > > > > > Koba, was this meant to be part of a series, or by itself? > > > > > > > Jerry, you're right, it's a part of the series. > > Hi Koba, > > If it is meant to be part of a series, where are patches 1 and 2? > The ccp patch has already been applied by the crypto maintainers if that > was meant to be part of a series with this patch. > > Regards, > Jerry Sorry, I misunderstood. actually, there's a mistake on the [3/3] part. I created patches for the mainline kernel before sending them to the upstream. Then I found the first has existed on the patchwork, so removed the [2/3] part for ccp patch and forgot to modify for this. Should I fix this and re-submit v2(also add those review-by)? > > > > > > > > > Regards, > > > Jerry > > > >
