Hi Mykhaylo, I'm really pleased that we're receiving contributions directly from Infineon and that your code will soon be merged into the mainline branch! I can only agree with what Oleksij said. Here are a few additional comments from my side.
Before you push your patches, please take a look at the coding style and the other development guidelines [1]. It's rather tedious to provide feedback on rules that have already been established. If in doubt, just ask or use recent code contributions as a guide. You should also consider providing test hardware to reviewers. In the past, testing on actual hardware has proved very helpful. One reason for this is that you may have different use cases, and your own hardware tests may not cover the use cases of other developers. A simple example: you use "only" GDB, but no Telnet or Tcl interfaces. Another reason for providing hardware is that it will enable regression testing after code and architecture rework in the future. In the past, reviewers were provided with hardware from other chip manufacturers for testing purposes. Naturally, hardware sponsorship is not subject to any conditions whatsoever for either party. Best regards Marc [1] https://openocd.org/doc/doxygen/html/index.html On Thu, 2026-05-21 at 08:37 +0000, Oleksij Rempel wrote: > Hi Mykhaylo, > > Sorry for spam, previous mail was from wrong mail address. > > Am 20.05.26 um 12:18 schrieb [email protected]: > > Sorry about that—I forgot to include a subject in this email. > > > > Best regards, > > > > Mykhaylo Lyubun > > > > Infineon > > Principal Engineer > > CSS ICW SW MTP DSPT PRGT > > Mobile: +380503177950<tel:+380503177950> > > [email protected]<mailto:[email protected]> > > > > > > From: Lyubun Mykhaylo (CSS ICW SW MTP DSPT PRGT) > > Sent: Wednesday, May 20, 2026 12:19 PM > > To: '[email protected]' > > <[email protected]> > > Cc: Sokhatska Vita (CSS ICW SW MTP DSPT) > > <[email protected]>; Ashton Skip (CSS ICW EODB) > > <[email protected]> > > Subject: > > > > Hello, > > > > I represent the SW Programming team at Infineon, we're looking to > > merge all our code from openOCD fork into the mainline. Most of our > > contributions are device support, but we've also made some > > improvements to the core files and structure. Right now, our plan > > is to test all our code against the mainline with our devices, and > > then start submitting merge requests to get everything integrated. > > We're aiming to get this done during Q3'26, so we'd really > > appreciate your support throughout the process. There are few > > questions so far: > > 1. How long does it usually take to process a merge request? > > 2. Is there a way we can speed up the review process or prioritize > > our merge requests? > > 3. How frequently do you release updates or make official releases > > from mainline? > > > > The reality is that OpenOCD maintenance is mostly a "hobby" done > after > hours, so reviewer capacity is quite limited. To answer your points: > > Timing: It’s unpredictable. It depends entirely on individual > maintainer > motivation, available spare time, and the initial quality of the > patches. > > Prioritization: Maintainer motivation is heavily affected by how > responsive the contributor is to feedback. To move faster, submit > small, > clean, incremental patches and address review comments quickly. > > Releases: These are infrequent and essentially "ready when they're > ready." > > If you are aiming for a Q3'26 deadline, I’d suggest hiring > specialized > help to navigate the upstreaming process. If no one else is > available, > my colleagues and I can support you officially through Pengutronix > (contact: [email protected]). > > Best regards, > Oleksij
