On 12/15/25 8:59 PM, Paulo Guilherme (MGC URPE SDN) wrote: > Hi everyone, >
Hi Paulo, > First, I apologize for my lack of knowledge of the process. The robot No worries, mistakes happen and we all make them from time to time, it's OK! > returned an error, and I'm unsure about where fail > > I suspect I did the process wrong (patch sequence): > > In patch v2 I had the following commits: > 0001-ovn-Move-run_idl_loop-function-to-lib-ovn-util.patch > 0002-ovn-ic-Introduce-incremental-processing-for-ovn-ic.patch > > Now in patch v3 I changed 2 another's files: > 0001-ovn-Move-run_idl_loop-function-to-lib-ovn-util.patch (no changes > compared to v2) > 0002-ovn-ic-Introduce-incremental-processing-for-ovn-ic.patch (no > changes compared to v2) > 0003-ovn-ic-Support-dumping-a-visual-representation-of-th.patch > 0004-docs-Update-OVN-I-P-Engine-documentation.patch > > But I renamed all patches for v3 in subject and resend all with command: > git send-email [email protected] <mailto:[email protected]> > 0001-ovn-Move-run_idl_loop-function-to-lib-ovn-util.patch 0002-ovn-ic- > Introduce-incremental-processing-for-ovn-ic.patch 0003-ovn-ic-Support- > dumping-a-visual-representation-of-th.patch 0004-docs-Update-OVN-I-P- > Engine-documentation.patch > I think the renaming wasn't exactly correct, they got routed to the OVS patchwork project: https://patchwork.ozlabs.org/project/openvswitch/list/?series=485415&state=* And that's because the patch emails had the "[PATCH x/4 v3]" prefix. By default all patches that _don't have_ "ovn" between squared brackets get routed to the OVS patchwork instance and the bot tries to apply them on top of the OVS main branch (or the branch specified between the brackets). The correct prefix should've been: "[PATCH ovn x/4 v3]". In order to avoid manually having to edit the generated patches you can configure your git repo to automatically add the correct prefix, as described in: https://github.com/ovn-org/ovn/blob/main/Documentation/internals/contributing/submitting-patches.rst#email-subject That is, run this inside your repo one time: git config set format.subjectprefix "PATCH ovn" Then, when generating the patch emails for a series, first rebase on top of the upstream origin/main branch and then just use format-patch/send-patch, e.g.: git fetch origin git rebase -i origin/main git format-patch -M origin/main --cover-letter --output-directory <patch-dir> This will generate patch emails (including a patch 0 cover letter) in the <patch-dir> directory. If the directory doesn't exist it will be created. Then edit the cover letter (patch 0) and send them all out: git send-email <patch-dir>/*.patch In your case, for the v3 series, you'd also have to add a "-v3", i.e.: git format-patch -v3 -M origin/main --cover-letter --output-directory <patch-dir> > My question is, in this context, the correct would be sending only 0003- > ovn-ic-Support-dumping-a-visual-representation-of-th.patch and 0004- > docs-Update-OVN-I-P-Engine-documentation.patch changing to v3 in Subject? > If patches 1 and 2 have not yet been applied to the OVN upstream tree (which is the case here) you'd have to include those too in the v3. > Thanks in advance! > No problem, hope this clarifies the process and don't hesitate to reach out if you have more questions. Regards, Dumitru > Em seg., 15 de dez. de 2025 às 11:55, 0-day Robot <[email protected] > <mailto:[email protected]>> escreveu: > > Bleep bloop. Greetings Paulo Guilherme Silva, I am a robot and I > have tried out your patch. > Thanks for your contribution. > > I encountered some error that I wasn't expecting. See the details > below. > > > git-am: > error: sha1 information is lacking or useless (lib/ovn-util.c). > error: could not build fake ancestor > hint: Use 'git am --show-current-patch=diff' to see the failed patch > Patch failed at 0001 ovn: Move run_idl_loop function to lib/ovn-util. > When you have resolved this problem, run "git am --continue". > If you prefer to skip this patch, run "git am --skip" instead. > To restore the original branch and stop patching, run "git am --abort". > > > Patch skipped due to previous failure. > > Please check this out. If you feel there has been an error, please > email [email protected] <mailto:[email protected]> > > Thanks, > 0-day Robot > > > > /‘Esta mensagem é direcionada apenas para os endereços constantes no > cabeçalho inicial. Se você não está listado nos endereços constantes no > cabeçalho, pedimos-lhe que desconsidere completamente o conteúdo dessa > mensagem e cuja cópia, encaminhamento e/ou execução das ações citadas > estão imediatamente anuladas e proibidas’./ > > / //‘Apesar do Magazine Luiza tomar todas as precauções razoáveis para > assegurar que nenhum vírus esteja presente nesse e-mail, a empresa não > poderá aceitar a responsabilidade por quaisquer perdas ou danos causados > por esse e-mail ou por seus anexos’./ > _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
