RE: [v2 PATCH] arm64: dts: stratix10: add new compatible for Intel SoCFPGA Stratix10 platform

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




> -----Original Message-----
> From: Krzysztof Kozlowski <krzysztof.kozlowski@xxxxxxxxxx>
> Sent: Friday, July 21, 2023 5:36 PM
> To: Li, Meng <Meng.Li@xxxxxxxxxxxxx>; dinguyen@xxxxxxxxxx;
> robh+dt@xxxxxxxxxx; krzysztof.kozlowski+dt@xxxxxxxxxx; conor+dt@xxxxxxxxxx;
> devicetree@xxxxxxxxxxxxxxx
> Cc: linux-kernel@xxxxxxxxxxxxxxx
> Subject: Re: [v2 PATCH] arm64: dts: stratix10: add new compatible for Intel
> SoCFPGA Stratix10 platform
> 
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and
> know the content is safe.
> 
> On 21/07/2023 11:29, Li, Meng wrote:
> >>>>>> NAK, don't fake reviews. This very impolite and destroys entire trust.
> >>>>>> The model of upstream collaboration depends on the trust, which
> >>>>>> is now gone for Windriver.
> >>>>>>
> >>>>>
> >>>>> No! I don't fake a tag.
> >>>>
> >>>> Really? Then I ask second time - from where did you get it? Provide a link.
> >>>>
> >>>
> >>> https://lore.kernel.org/lkml/20230718030851.2014306-1-Meng.Li@windri
> >>> ve
> >>> r.com/T/
> >>
> >> So where is it? You pointed to your email. Where is the tag?
> >>
> >
> > Sorry! Maybe I have wrong understanding about TAG.
> > From my perspective, If reviewers ask question or give some advices to the
> patch, I need to add the tag to v2.
> 
> This is some crazy idea. So you want to sprinkle some tags, just because
> someone disagrees with your patch and explicitly gives you a NAK, which means
> NOT-Ack, Not-acknowledge, not accepted, not in good shape.
> 
> I actually wonder why adding an acknowledging tag for the patch, if I disagreed
> and gave you NAK. Following your logic, this should be a NAK tag. This I could
> understand. But giving acknowledge when I clearly said patch is wrong?
> 

Very sorry for wasting your time because of lack of understanding about upstream rules.
And thanks for many explanations patiently, this will help me make progress.

> Read all process documents before submitting new patches:
> https://www.kernel.org/doc/html/latest/process/
> 

Ok! I will check these docs.

Thanks,
Limeng

> > If it is not allowed, I apologize for that.
> 
> Best regards,
> Krzysztof





[Index of Archives]     [Device Tree Compilter]     [Device Tree Spec]     [Linux Driver Backports]     [Video for Linux]     [Linux USB Devel]     [Linux PCI Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Yosemite Backpacking]


  Powered by Linux