NAK: [P][PATCH 1/1] UBUNTU: [Config] Change CONFIG_CRYPTO_HMAC_S390 to m for s390x

[Agathe Porte]

Hello,

2025-02-06 18:28 CET, Juerg Haefliger:
> On Thu, 6 Feb 2025 14:16:31 +0100
> Agathe Porte <agathe.porte at canonical.com> wrote:
> 
> > 2025-02-06 14:03 CET, Frank Heimes:
> > > Hi,
> > > the bug was still marked as private, it's now public.
> > > Apologize, please try again.  
> > 
> > TL;DR: please send same patch as v2.
> > 
> > Mhm, I probably was to fast and the NAK: should have been a Re:.
> > I can now access the bug but your patch is "flagged" with NAK.
> > 
> > I would send an ACK but due to the way how some of us filter emails you
> > should send a v2 patch. This is because as soon as a patch gets an NAK
> > it automatically goes to the bin for some users like me.
> 
> That is a problem on our side, not the submitters. We should not punish
> submitters for our mistakes. Maybe send an UNACK or something and filter on
> that.

I agree.

We need to find something commonly used by all members and provide
tooling to work around it.

Part of my answer was directed not for me to not ACK it, but because it
might have been difficult to collect a second ACK from other people
given the thread was tainted.

So to give the best chances to the author I suggested to resend to reset
the taint.