Recommended state for debugging/hack patches?

Carl-Daniel Hailfinger c-d.hailfinger.devel.2006 at
Fri Sep 25 08:36:13 EST 2009


this is a policy question and I'm not sure about the answer.

There are some patches in our patchwork instance which will never be
merged but are very useful for some users/developers.
For example, there is a patch abusing the I/O address of the serial port
to access the flash controller on mainboards with broken southbridge
resource allocation. It is the only way to recover/flash some
mainboards, but at the same time the patch has to kill the serial
console which is totally undesirable on every system which is not
already broken. Another example would be a patch changing the default
log level all the way to DEBUG_SPEW.

Neither of the existing states (New, Not Applicable, ...) seems to fit
this particular purpose and I believe we are not the only project with
such patches.
Which state would you recommend for such patches? Or should we create a
new state?


More information about the Patchwork mailing list