On Fri, Apr 19, 2024 at 05:54:58AM +0000, Liuye wrote: > @Greg KH > > This issue still needs to be resolved, but I don't know how to do it. > Please tell me an effective strategy. How should feedback be given to make it > effective for you? > There is already an approval process for external emails in the current > company. > And a review mechanism has been added within the team. And internal training > is provided. > The previous mentioned has been completed. What else needs to be done?
What would you want to see if you were in my position here? Some sort of "proof" that this really is the case? A discussion with your company legal group about this? A discussion with your legal group and the open source legal community about how they have structured all of this so that it will not happen again and a discussion about how this did happen (i.e. a blameless post-mortum)? A signed-off-by on your next patch from a lawyer in that group? In other words, what does your legal group think would be sufficient here? thanks, greg k-h _______________________________________________ Kgdb-bugreport mailing list Kgdb-bugreport@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
