Comment 5 for bug 1869123

I just wanted to start to work on the SRU of "powerpc/powernv: Return for invalid IMC domain" to bionic. First of all I looked up when the patch got upstream accepted and when it landed in linux (master):
$ git tag --contains b59bd3527fe3
v5.2-rc3

With that it must be already in Eoan, since Eoan was shipped with a kernel 5.3 (notice that we always need to SRU from newest to oldest - incl. all Ubuntu releases that are in service).
Hence looking it up in Eoan (master):
$ git tag --contains b59bd3527fe3
Ubuntu-5.2.0-8.9
...
Ubuntu-5.3.0-45.37
Means it is already in Eoan - so we are good there.

Now checking bionic (master):
$ git log --oneline --grep "powerpc/powernv: Return for invalid IMC domain"
062b1248da71 powerpc/powernv: Return for invalid IMC domain
$ git tag --contains 062b1248da71
Ubuntu-4.15.0-59.66
...
Ubuntu-4.15.0-94.95
So it is already in bionic, too!

How did it found it's way into bionic:
$ git show 062b1248da71 | grep BugLink
    BugLink: https://bugs.launchpad.net/bugs/1838824
$ lp-list-bugs 1838824
Bug 1838824: Bionic update: upstream stable patchset 2019-08-02
  linux (Ubuntu): Fix Released
  linux (Ubuntu Bionic): Fix Released

In summary the commit/patch "powerpc/powernv: Return for invalid IMC domain" landed in bionics kernel 'Ubuntu-4.15.0-59.66' via the bionic upstream stable patchset from 2019-08-02.

If this patch/commit is the right one, then there seems to be nothing todo here.