[RFC] filter function for submaintainers

Jeremy Kerr jk at ozlabs.org
Thu Apr 7 12:00:06 EST 2011

Hi Uwe,

> The problem (admittedly only from a quick glance at
> patchwork.ozlabs.org) I see is that it's not possible to reliably filter
> patches by directory name. (Or maybe I'm just to stupid to find the
> right knob, I tried searching for "drivers/net/ehea" in the netdev
> project, got a few hits, but e.g.
> http://patchwork.ozlabs.org/patch/89837/ wasn't listed. My guess is that
> the search only checks subject and commit log?)

At present, the search only covers the patch subject.

> For us I think this is a crucial function, because the imx patches are
> usually sent to the linux-arm-kernel mailing list where most patches
> don't touch the files we are responsible for.

It sounds like a separate linux-imx patchwork instance would suit better
- this would mean you don't have to constantly apply filters to get the
patches that you're interested in.

I'm very happy to set up a patchwork instance on ozlabs.org for you; but
(as you've mentioned) we'd need to filter-out the imx patches from the
rest of the l-a-k content that you're not interested in tracking.

Most projects (eg linux-davinci, linux-omap) do this by using a separate
mailing list; I assume you'd rather keep your patches on the main ARM
list, correct?

Since this is a one-off, I think an external program to filter relevant
patches from l-a-k would be best. This would check the diffstat for
interesting paths, then conditionally feed the patch to the patchwork

Would this suit? Are you OK with including patches that are not
necessarily imx-specific, but touch imx-related code (eg,
architecture-wide code cleanups)?



More information about the Patchwork mailing list