From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751270AbdGLEuv (ORCPT <rfc822;w@1wt.eu>);
        Wed, 12 Jul 2017 00:50:51 -0400
Received: from ozlabs.org ([103.22.144.67]:49229 "EHLO ozlabs.org"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1750705AbdGLEuu (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 12 Jul 2017 00:50:50 -0400
Date: Wed, 12 Jul 2017 14:50:48 +1000
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
        Greg KH <gregkh@linuxfoundation.org>,
        Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
        Andrew Morton <akpm@linux-foundation.org>,
        Arnd Bergmann <arnd@arndb.de>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Char/Misc driver patches for 4.12-rc1
Message-ID: <20170712145048.501ec22f@canb.auug.org.au>
In-Reply-To: <1494094356.2407.20.camel@HansenPartnership.com>
References: <20170505001808.GA16769@kroah.com>
        <CA+55aFx-ZxaveO=_YMaPb+bO8tia8eKZik16zVt83Ewkrj41og@mail.gmail.com>
        <1494000006.2399.7.camel@HansenPartnership.com>
        <20170505163846.GA31211@kroah.com>
        <CA+55aFxX6aH8nnVUwyFvNkjg5pKD0LWYA56nhPtUz81sxi7LWg@mail.gmail.com>
        <20170506150911.1612bb15@canb.auug.org.au>
        <CA+55aFzZhbWv7cYN8q1yZJmzfhwKJWEmL6YW6BLxpPctG-_8SA@mail.gmail.com>
        <1494094356.2407.20.camel@HansenPartnership.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hi all,

On Sat, 06 May 2017 11:12:36 -0700 James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
>
> What about resending the conflict reminders at -rc7 ... that way we
> only have a week or two to forget again?

OK, I attempted to do that this time ... I wonder if it made a
difference :-)

> The other issue is that one of the potential trees only got notified
> directly (the char-misc one) because the tpmdd tree takes an indirect
> pull route.  I'm not sure what we can do about this one.

I have also tried (in most cases) to notify the effected maintainers
that ask Linus to pull.
 
-- 
Cheers,
Stephen Rothwell