> > > > > It doesn't apply to our for-next branch. > > > > Sorry to hear that. I've rebased the series on mainline 5.5-rc7. > > > > Should I > > > rebase it on for-next branch? > > > > > > You should always base your branch on the for-next (whatever it's > > > being > > > called) of the subsystem your series against of. > > > > Hi Andy, > > > > The current series has a dependency on Tiger Lake and Elkhart Lake patche > which is merged in to mainline. > > > > (554f269f0f38 platform/x86: intel_pmc_core: Add Intel Elkhart Lake > > support 49a437941c3f platform/x86: intel_pmc_core: Add Intel Tiger > > Lake support > > 6268c0b278b5 platform/x86: intel_pmc_core: Make debugfs entry for > > pch_ip_power_gating_status conditional > > e39854781830 platform/x86: intel_pmc_core: Create platform dependent > > bitmap structs > > b1cb33dae414 platform/x86: intel_pmc_core: Clean up: Remove comma > > after the termination line) > > > > But they are not available in for-next branch. I am confused, how that could > be the case. For me to base the current series on for-next branch, the > dependency patch series should be available in for-next branch. > > I'm wondering how did you check it? > The branch location is in this [1] tree. Thank you for your patience Andy. I apologize for the mishap as I was checking in the wrong tree. I have rebased the series on for-next branch on right tree this time and sent v2. > > [1]: http://git.infradead.org/linux-platform-drivers-x86.git > > -- > With Best Regards, > Andy Shevchenko >
