On Thu, Jan 30, 2020 at 10:53:46AM +0100, Petr Mladek wrote: > On Wed 2020-01-29 09:59:51, Josh Poimboeuf wrote: > > In retrospect, the prerequisites for merging it should have been: > > OK, let me do one more move in this game. > > > > 1) Document how source-based patches can be safely generated; > > I agree that the information are really scattered over many files > in Documentation/livepatch/. Once again you're blithely ignoring my point and pretending I'm saying something else. And you did that again further down in the email, but what's the point of arguing if you're not going to listen. This has nothing to do with the organization of the existing documentation. When did I say that? Adding the -flive-patching flag doesn't remove *all* function-ABI-breaking optimizations. It's only a partial solution. The rest of the solution involves tooling and processes which need to be documented. But you already know that. If we weren't co-maintainers I would have reverted the patch days ago. I've tried to give you all the benefit of the doubt. But you seem to be playing company politics. I would ask that you please put on your upstream hats and stop playing politics. If the patch creation process is a secret, then by all means, keep it secret. But then keep your GCC flag to yourself. -- Josh
