linux-kernel - Re: [git pull] habanalabs fixes for 5.1 rc2/3

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]

Message-ID: <CAFCwf106g4jcjZkERQauAmKFpnTrOo37ufJ1treMA8LBmP+jhQ@mail.gmail.com>
Date:   Tue, 26 Mar 2019 09:54:20 +0200
From:   Oded Gabbay <oded.gabbay@...il.com>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     "Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>
Subject: Re: [git pull] habanalabs fixes for 5.1 rc2/3

On Tue, Mar 26, 2019 at 9:53 AM Greg KH <gregkh@...uxfoundation.org> wrote:
>
> On Thu, Mar 21, 2019 at 05:28:16PM +0200, Oded Gabbay wrote:
> > Hi Greg,
> >
> > A couple of important fixes for habanalabs driver:
> >
> > - Fix host crash upon resume after suspend
> > - Fix MMU related bugs which result in user's jobs getting stuck
> > - Fix race between user context cleanup and hard-reset which results in
> >   host crash
> > - Fix sparse warning
> >
> > Thanks,
> > Oded
> >
> > The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
> >
> >   Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
> >
> > are available in the Git repository at:
> >
> >   git://people.freedesktop.org/~gabbayo/linux tags/misc-habanalabs-fixes-2019-03-21
> >
> > for you to fetch changes up to 2198b040b98cfbed62716692a34eb971e0383f93:
> >
> >   habanalabs: cast to expected type (2019-03-03 10:23:29 +0200)
> >
> > ----------------------------------------------------------------
>
> There is no text at all in your tag :(
>
> You need to put something there, like "here are the fixes that do..." or
> some sort of explaination for why this set of patches need to be pulled
> in.  That way it shows up in the merge commit properly.
>
> Can you fix this up and resend?
>
> thanks,
>
> greg k-h

Ok, didn't know that. I'll get to it right away.

Oded