Message ID | 26892a0a-c6c4-6409-44cf-1f407ac21482@ti.com (mailing list archive) |
---|---|
State | Mainlined, archived |
Commit | 49b654fd43b29e8decaa38035eed9ca8f221e48a |
Headers | show |
Series | [GIT,PULL] DaVinci SoC updates for v5.1 (part 3) | expand |
On 19/02/19 9:05 PM, Sekhar Nori wrote: > Hi Arnd, Olof, > > This is a late request to pull some further SoC updates for DaVinci. > The patches have been in the works for a while, but we received the > final maintainer acks only yesterday. > > I hope we can merge this for v5.1. We have further clean-ups for > mach-davinci planned, and it will be good to get this out of the > way. > > I have run randconfig builds with a previous version of this series. > I am running afresh with this branch too. The branch merges without This is done and no new randconfig issues were found with this series (10 random + 1 allnoconfig builds) Thanks, Sekhar
On Wed, Feb 20, 2019 at 12:08 PM Sekhar Nori <nsekhar@ti.com> wrote: > > On 19/02/19 9:05 PM, Sekhar Nori wrote: > > Hi Arnd, Olof, > > > > This is a late request to pull some further SoC updates for DaVinci. > > The patches have been in the works for a while, but we received the > > final maintainer acks only yesterday. > > > > I hope we can merge this for v5.1. We have further clean-ups for > > mach-davinci planned, and it will be good to get this out of the > > way. > > > > I have run randconfig builds with a previous version of this series. > > I am running afresh with this branch too. The branch merges without > > This is done and no new randconfig issues were found with this series > (10 random + 1 allnoconfig builds) I've pulled the branch into arm/late for now. All the patches look really nice, so agree we should have them in v5.1, but given the timing I wasn't quite comfortable enough with having them in arm/soc right away, in case something does come up. If all goes well, we might end up merging it into arm/soc before sendinng out the pull requests, but it depends a bit on the timing of the merge window and how much more testing I can get done. If it's not part of the initial pull requests, we can aim for sending this in the second half of the merge window. Arnd