On Fri, Apr 7, 2023 at 9:00 AM Tim Newsome wrote:
>
>
>> Can you use Checkpatch-ignore in the fork?
>>
>
> Possibly. Part of the problem is that I haven't figured out in the github
> action how to find which changes are part of the pull request. Erhan
> suggested some clever git commands in
>
On Fri, Apr 7, 2023 at 7:46 AM Antonio Borneo
wrote:
> indeed cherry-picking old patches can result in checkpatch screaming
> hysterically !
>
Note this is not the result of cherry-picking. It's simply merging all of
mainline openocd up to a certain change into riscv-openocd.
> Can you use
Hi Antonio
Thanks a lot for the quick reply.
> Can you use Checkpatch-ignore in the fork?
Maybe that would be a more pragmatic option alright.
Let me check with Tim Newsome who leads the work on the RISC-V OpenOCD fork.
Unless he's reading this and wants to pitch in himself? :-)
Thanks again.
On Fri, Apr 7, 2023 at 1:13 PM Tommy Murphy wrote:
>
> Hi there
>
> As many of you probably know, RISC-V OpenOCD development continues to be done
> on this fork:
>
> https://github.com/riscv/riscv-openocd
>
> Periodically, changes here are upstreamed to the "main" OpenOCD project
> and/or
Hi there
As many of you probably know, RISC-V OpenOCD development continues to be done
on this fork:
* https://github.com/riscv/riscv-openocd
Periodically, changes here are upstreamed to the "main" OpenOCD project and/or
patches upstream are pulled down to more closely sync/align the two
