mirror of https://lore.kernel.org/lkml/
 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 pull request for kernel 5.9-rc1 (resend)
Date: Fri, 24 Jul 2020 11:32:59 +0200	[thread overview]
Message-ID: <20200724093259.GB4116407@kroah.com> (raw)
In-Reply-To: <20200723191525.GA24516@ogabbay-VM>

On Thu, Jul 23, 2020 at 10:15:25PM +0300, Oded Gabbay wrote:
> Hello Greg,
> 
> (Re-sending this pull request)
> 
> This is habanalabs pull request for the merge window of kernel 5.9. It
> contains many small improvements to common and GAUDI code. Details are in
> the tag.
> 
> Thanks,
> Oded
> 
> The following changes since commit 7a4462a96777b64b22412f782de226c90290bf75:
> 
>   misc: rtsx: Use standard PCI definitions (2020-07-22 13:39:31 +0200)
> 
> are available in the Git repository at:
> 
>   git://people.freedesktop.org/~gabbayo/linux tags/misc-habanalabs-next-2020-07-23

{sigh}

Commit: 961a7325e670 ("habanalabs: Fix memory leak in error flow of context init")
	Fixes tag: Fixes: 786c94810698 ("habanalabs: Use pending cs amount per asic")
	Has these problem(s):
	        - Subject does not match target commit subject
	          Just use
		                git log -1 --format='Fixes: %h ("%s")'

The scripts I use to check this are here:
	https://github.com/gregkh/gregkh-linux/blob/master/work/verify_fixes.sh
	https://github.com/gregkh/gregkh-linux/blob/master/work/verify_signedoff.sh

And note, if I ignore these errors, you will just get the same response
from Stephen when it hits linux-next :(

thanks,

greg k-h

  reply	other threads:[~2020-07-24  9:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-23 19:15 Oded Gabbay
2020-07-24  9:32 ` Greg KH [this message]
2020-07-24 11:35   ` Oded Gabbay
2020-07-24 13:23     ` Greg KH

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=20200724093259.GB4116407@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome