All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Oded Gabbay <oded.gabbay@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [git pull] habanalabs fixes for 5.1 rc2/3
Date: Tue, 26 Mar 2019 16:53:24 +0900	[thread overview]
Message-ID: <20190326075324.GA25748@kroah.com> (raw)
In-Reply-To: <20190321152816.GA1381@ogabbay-VM>

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

  reply	other threads:[~2019-03-26  7:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-21 15:28 [git pull] habanalabs fixes for 5.1 rc2/3 Oded Gabbay
2019-03-26  7:53 ` Greg KH [this message]
2019-03-26  7:54   ` Oded Gabbay

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190326075324.GA25748@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oded.gabbay@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.