On Thu, Apr 28, 2022 at 02:48:53AM +0300, Kirill A. Shutemov wrote:
> Right. That's true. But having goto here makes patch 5/12 a bit cleaner.
Ok, let's take our time machine and go into the future:
This patch is in git, there's no concept of "next patch" anymore - and
someone is staring at it for whatever reason.
Someone is wondering: why the hell was this done this way? And which
is that "next patch"? Someone probably needs to sort them in the
application order to figure out which next patch the author is talking
about...
See what I mean?
Also, if this hunk
+
+ if (IS_ENABLED(CONFIG_UNACCEPTED_MEMORY))
+ status = allocate_unaccepted_memory(params, nr_desc, map);
+
is what this is all about, then no, this confusion is not even worth it
- please make sure your patches make sense on their own.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
