Hi Mykhaylo,

To clarify the context: I replied from my private email address because my involvement with OpenOCD is mostly a personal hobby. However, I am part of the Linux kernel team at Pengutronix.

To give you a high-level overview, Pengutronix supports customers across different levels-from hardware and design assistance to base systems, bootloaders, the Linux kernel, and BSPs.

Regarding upstreaming, we typically take over the heavy lifting. The workflow usually looks like this:
- You share your internal repository/fork with us.
- We review the code and refactor or adapt it to meet the mainline project's strict standards. - We handle splitting the code into acceptable patch series, submitting them, and managing all communication and iterations with the community until the code is merged. - We do this regularly for our customers across various projects, including the Linux kernel, Barebox, GStreamer, and many others.

More information can be found here:
https://pengutronix.de/en/

Here are some examples of our work on the kernel site:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/?h=v7.1-rc4&qt=author&q=pengutronix

Best regards,
Oleksij

Am 21.05.26 um 10:45 schrieb [email protected]:
Hi Oleksij,

Thank you for getting back to me. I’d appreciate a bit more clarity on how 
Pengutronix’s workflow operates. When you mention “hiring specialized help,” 
does that mean they assist with code reviews, or do we share our repository, 
and they handle merging our code into the mainline? Could you give me a 
high-level overview of the types of services they offer? I need this 
information to discuss our options with my managers.

Best regards,

Mykhaylo Lyubun
Infineon
Principal Engineer
CSS ICW SW MTP DSPT PRGT
Mobile: +380503177950
[email protected]
-----Original Message-----
From: Oleksij Rempel <[email protected]>
Sent: Thursday, May 21, 2026 11:37 AM
To: Lyubun Mykhaylo (CSS ICW SW MTP DSPT PRGT) <[email protected]>; 
[email protected]
Cc: Ashton Skip (CSS ICW EODB) <[email protected]>; Sokhatska Vita (CSS ICW SW 
MTP DSPT) <[email protected]>
Subject: Re: The Infineon fork of OpenOCD has now been merged into the mainline 
OpenOCD project.

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


Reply via email to