Date: Fri, 1 Sep 2017 19:15:18 +0200
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Martyn Welch <martyn.welch@collabora.co.uk>
Cc: Linux Driver Project Developer List <devel@driverdev.osuosl.org>,
        LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] VME Subsystem patches for 4.13-rc7
Message-ID: <20170901171518.GA31446@kroah.com>
References: <20170901170848.GA30668@hermes.home>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170901170848.GA30668@hermes.home>
User-Agent: Mutt/1.8.3 (2017-05-23)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1073
Lines: 31

On Fri, Sep 01, 2017 at 06:08:48PM +0100, Martyn Welch wrote:
> The following changes since commit 0f9b011d3321ca1079c7a46c18cb1956fbdb7bcb:
> 
>   driver core: bus: Fix a potential double free (2017-08-31 18:57:30 +0200)
> 
> are available in the git repository at:
> 
>   https://gitlab.collabora.com/martyn/linux.git tags/vme-next-4.13-rc7
> 
> for you to fetch changes up to 92203389d32f83f71cb1944840af31ffb3a42e6f:
> 
>   vme: tsi148: Adjust 14 checks for null pointers (2017-09-01 14:08:46 +0100)
> 
> ----------------------------------------------------------------
> VME Subsystem changes for driver-core-next v4.13-rc7
> 

driver-core?  No, you should make this against char-misc-next.  But
really, just make it against 4.13-rc7 and then it shouldn't matter what
tree I pull it into.

Also, can you provide more merge text information?  A one line really
doesn't say what is going on here.  Look on lkml for lots of examples of
what people put here.

As an example, see the emails I send to Linus for when I ask him to pull
the char-misc tree.

thanks,

greg k-h