On Wed, Dec 5, 2018 at 1:39 AM Andy Shevchenko <andy.shevchenko@xxxxxxxxx> wrote: > > On Tue, Dec 4, 2018 at 6:58 PM Frank Lee <tiny.windzz@xxxxxxxxx> wrote: > > > $ git br -r > > origin/HEAD -> origin/master > > origin/fixes > > origin/for-next > > origin/master > > origin/review-andy > > $ git remote set-branches --add origin for-next > > $ git br -vv > > * for-next 651022382c7f [origin/for-next] Linux 4.20-rc1 > > Here is the problem, > > For a few days at least we have > 4ecd94b8e13b (HEAD -> for-next) platform/x86: dell-laptop: Mark > expected switch fall-throughs > > > $ git apply ../../0001-platform-x86-convert-to-DEFINE_SHOW_ATTRIBUTE.patch > > $ git st > > On branch for-next > > Your branch is up to date with 'origin/for-next'. > > > > Changes not staged for commit: > > (use "git add <file>..." to update what will be committed) > > (use "git checkout -- <file>..." to discard changes in working directory) > > > > modified: drivers/platform/x86/intel_pmc_core.c > > modified: drivers/platform/x86/intel_telemetry_debugfs.c > > > > no changes added to commit (use "git add" and/or "git commit -a") > > > Andy,I don't know why. > > Is there a problem with my operation? > > Definitely. Where can I find the correct git repository？ I haven't found the correct one for a long time, which include the commit(4ecd94b8e13b ) you said. MBR, Yangtao > > -- > With Best Regards, > Andy Shevchenko
