Hello Greg, On 12/1/22 14:21, Greg KH wrote: [...] >>>> This patchset was sent using the b4 tool and I can't control this >>>> aspect. Everyone mentioned in the patches gets the whole set. >>> >>> Fair enough, but watch out, bots will report this as being a problem as >>> they can't always read through all patches in a series to notice this... >>> >> >> Konstantin, >> >> Can you add a rule in b4 to exclude stable@xxxxxxxxxxxxxxx >> (stable@xxxxxxxxxx as well?) from getting the whole patchset? > > stable@xxxxxxxxxx is a pipe to /dev/null so that's not needed to be > messed with. > > As for this needing special casing in b4, it's rare that you send out a > patch series and only want 1 or 2 of them in stable, right? > Not really, it's very common for a patch-series to contain fixes (that could go to stable if applicable) and change that are not suitable for stable. The problem as Noralf mentioned is that the b4 tool doesn't seem to allow Cc'ing individual patches to different recipients, and everyone get the whole set. So either b4 needs to have this support, exclude stable@xxxxxxxxxxxxxxx when sending a set or stable@xxxxxxxxxxxxxxx ignore patches without a Fixes: tag. -- Best regards, Javier Martinez Canillas Core Platforms Red Hat
