On Tue, May 08, 2018 at 11:40:52AM +1000, Stephen Rothwell wrote: > Hi all, > > On Tue, 08 May 2018 01:36:25 -0000 Patchwork <patchwork@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > > > == Series Details == > > > > Series: linux-next: build failure after merge of the drm-intel tree > > URL : https://patchwork.freedesktop.org/series/42839/ > > State : failure > > Blah, blah :-) > > Can someone please arrange for my linux-next merge fix patches to not > be fed into your patchwork/ci as they will never work out side > linux-next ... Hey, Sorry for clotting your inbox with those mails but I have to ask how annoying is getting those results? If it's bearable I would prefer to not introduce special cases basing on contents of the mbox and/or its author. As of our CI we are not really that much concerned with wasting time on something that wasn't meant to be tested - such patches are extremely rare. If this is necessary - do you have any suggestion how it should be done? Filtering by "linux-next" in the Subject? By your name? Email address? Is it the case that linux-next can appear only in untestable patches? Is silently ignoring such a patch by the CI really okay? Maybe we should introduce [NOCI] subject tag? Would you remember to include it? As of instant solution - you can include "X-Patchwork-Hint: comment" in the headers, so patchwork won't recognize your email as a patch. -- Cheers, Arek _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
