On Thu, Oct 29, 2020 at 04:45:52PM -0700, Nick Desaulniers wrote:
On Thu, Oct 29, 2020 at 4:36 PM Sasha Levin <sashal@xxxxxxxxxx> wrote:
On Thu, Oct 29, 2020 at 11:05:01AM -0700, Nick Desaulniers wrote:
>Hi Jian,
>Thanks for proactively identifying and requesting a backport of
>44623b2818. We'll need it for Android as well soon.
>
>One thing I do when requesting backports from stable is I checkout the
>branch of the stable tree and see if the patch cherry picks cleanly.
btw, an easy way to get an idea of possible dependencies is to look at
the dependency repo :) For this commit on 5.4:
https://git.kernel.org/pub/scm/linux/kernel/git/sashal/deps.git/plain/v5.4/44623b2818f4a442726639572f44fd9b6d0ef68c
Why you guys never tell me this before? :P Very cool, how is the
dependency chain built? Is it built for every commit?
git bisect run for each commit on each branch we have. I have a little
stable-deps tool that looks something like this to make it easy:
ver=$(make SUBLEVEL= kernelversion)
cmt=$(git rev-parse $1)
for i in $(curl -s https://git.kernel.org/pub/scm/linux/kernel/git/sashal/deps.git/plain/v$ver/$cmt | awk {'print $1'}); do
stable commit-in-tree $i
if [ $? -eq 1 ]; then
continue
fi
git ol $i
done
--
Thanks,
Sasha