On Thu, Apr 05, 2018 at 06:40:06AM +0000, Sasha Levin wrote: > On Thu, Apr 05, 2018 at 08:30:10AM +0200, Greg KH wrote: > >On Thu, Apr 05, 2018 at 01:33:35AM +0000, Sasha Levin wrote: > >> Hi Finn Thain. > >> > >> [This is an automated email] > >> > >> This commit has been processed by the -stable helper bot and determined > >> to be a high probability candidate for -stable trees. (score: 3.6525) > >> > >> The bot has tested the following trees: v4.15.15, v4.14.32, v4.9.92, v4.4.126, > >> > >> v4.15.15: Build OK! > >> v4.14.32: Build OK! > >> v4.9.92: Build OK! > >> v4.4.126: Build OK! > >> > >> Please let us know if you'd like to have this patch included in a stable tree. > > > >Did this bot respond to the whole series here, or the 00/12 patch? :) > > I'm experimenting with an idea that involves squashing a series of > commits into a single commit and running it through the NN that way. > > I figured it might make sense since when people mail patches this way > there's usually dependencies between them, so if a random patch in the > series got tagged for stable, we'll need to bring in the rest of the > series as well. > > So yes, in this case the entire series was identified by the NN as > stable material. You can also see that there are separate mails for > individual patches in the series - they acts as a sort of a fallback > saying "maybe you don't want the whole series, but consider these > as individual patches" (also gives a hint as to why the entire series > was selected). Ah, very nice stuff! Thanks for the explaination. greg k-h