On 26/03/2024 21:23, Krzysztof Kozlowski wrote:
> Merging
> =======
> All further patches depend on the first amba patch, therefore please ack
> and this should go via one tree.
>
> Description
> ===========
> Modules registering driver with amba_driver_register() often forget to
> set .owner field.
>
> Solve the problem by moving this task away from the drivers to the core
> amba bus code, just like we did for platform_driver in commit
> 9447057eaff8 ("platform_device: use a macro instead of
> platform_driver_register").
>
> Best regards,
I tried to submit this series to Russell patch tracker and failed. This
is ridiculous. It's 2024 and instead of normal process, like every other
maintainer, so b4 or Patchwork, we have some unusable system rejecting
standard patches.
First, it depends some weird, duplicated signed-off-by's. Second it
submitting patch-by-patch, all with clicking on some web (!!!) interface.
I did it, clicked 19 times and system was happy... but then on email
said the patches were rejected. Couldn't tell it after submitting first
patch via the web?
That's the response:
-------------
Your patch has not been logged because:
Error: Please supply a summary subject line briefly describing
your patch.
Error: Please supply a "KernelVersion: " tag after "PATCH FOLLOWS" or
"---".
Error: the patch you are submitting has one or more missing or incorrect
Signed-off-by lines:
- author signoff <krzkreg@xxxxxxxxx> is missing.
Please see the file Documentation/SubmittingPatches, section 11
for details on signing off patches.
Please see https://www.armlinux.org.uk/developer/patches/info.shtml
for more information.
-------------
This is unbelievable waste of time. I am not going to use this tracker.
It's huge obstacle and huge waste of submitters time.
Best regards,
Krzysztof
