Hi,
On Tue, Jun 26, 2018 at 8:02 AM, Mark Brown <broo...@kernel.org> wrote:
> On Tue, Jun 26, 2018 at 08:00:29AM -0700, Doug Anderson wrote:
>> On Tue, Jun 26, 2018 at 5:07 AM, Mark Brown <broo...@kernel.org> wrote:
>
>> > Please do not submit new versions of already applied patches, please
>> > submit incremental updates to the existing code. Modifying existing
>> > commits creates problems for other users building on top of those
>> > commits so it's best practice to only change pubished git commits if
>> > absolutely essential.
>
>> Sorry, wasn't suggesting making any changes to those two patches, just
>> was noting the dependency. ...but, as you said, the two dependent
>> patches have already landed and I just didn't notice. :( Sorry for
>> the noise.
>
> Ah, so there's no revisions that need merging? That's great.
Right. So all that's left to do is decide if ${SUBJECT} patch is
ready to land and how to land it. Andy has landed RPMh into his
for-next tree. You can see it at
<https://git.kernel.org/pub/scm/linux/kernel/git/agross/linux.git/log/?h=for-next>.
I think he's still planning on re-shuffling his tree a bit. When he
does this, do you need him to put the RPMh patches somewhere you can
merge into your tree?
Thanks!
-Doug
