> From: Sasha Levin <sashal@xxxxxxxxxx> > Sent: Thursday, September 5, 2019 8:44 AM > On Tue, Sep 03, 2019 at 12:23:16AM +0000, Dexuan Cui wrote: > >This is needed for hibernation, e.g. when we resume the old kernel, we need > >to disable the "current" kernel's hypercall page and then resume the old > >kernel's. > > Hi Dexuan, > > When sending patches upstream, please make sure you send them to all > maintainers and mailing lists that it needs to go to according to > MAINTAINERS/get_maintainers.py rather than cherry-picking names off the > list. > > This is specially important in subsystems like x86 where it's a group > maintainers model, and it's very possible that Thomas is sipping > margaritas on a beach while one of the other x86 maintainers is covering > the tree. > > This is quite easy with git-send-email and get_maintainers.py, something > like this: > > git send-email --cc-cmd="scripts/get_maintainer.pl --separator=, > --no-rolestats" your-work.patch > > Will do all of that automatically for you. > Sasha Thanks for the reminder, Sasha! I didn't know the very useful parameter of git-send-email. :-) I'm going to post v5 with the parameter. BTW, I'll split v4 into 2 patchsets. Patchset #1 consists of the first 3 patches of v4, and should go through the tip.git tree (I need to rebase it to the latest timers/core branch due to a conflict). Patchset #2 consists of the remaining 9 patches and can go through the hyperv tree. Thanks, -- Dexuan
