linux-kernel - Re: [GIT PULL] VME Subsystem patches for 4.13-rc7

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Fri, 1 Sep 2017 19:15:18 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Martyn Welch <martyn.welch@...labora.co.uk>
Cc:     Linux Driver Project Developer List <devel@...verdev.osuosl.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] VME Subsystem patches for 4.13-rc7

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