From: Oded Gabbay <oded.gabbay@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] habanalabs pull request for kernel 5.9-rc1
Date: Thu, 23 Jul 2020 22:04:23 +0300 [thread overview]
Message-ID: <CAFCwf10kNLNbeb0g8_Aujup+jAdBPGwyKODTc53iK+N0dKCJNQ@mail.gmail.com> (raw)
In-Reply-To: <20200723185931.GC3768907@kroah.com>
On Thu, Jul 23, 2020 at 9:59 PM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Thu, Jul 23, 2020 at 06:29:38PM +0300, Oded Gabbay wrote:
> > Hello Greg,
> >
> > 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
>
> My scripts spit out the following error when I tried to push this out:
>
> Commit: fc83dc9787ce ("habanalabs: Fix memory leak in error flow of context init")
> Fixes tag: Fixes: "habanalabs: Use pending cs amount per asic"
> Has these problem(s):
> - No SHA1 recognised
>
>
> Your line:
> Fixes: "habanalabs: Use pending cs amount per asic"
>
> should have a sha1 in it :(
>
> And use the proper format as well.
>
> Can you fix this up and resend the pull request?
>
> thanks,
>
> greg k-h
Sorry, my bad, I'll fix this right away.
Oded
prev parent reply other threads:[~2020-07-23 19:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 15:29 [git pull] habanalabs pull request for kernel 5.9-rc1 Oded Gabbay
2020-07-23 18:59 ` Greg KH
2020-07-23 19:04 ` Oded Gabbay [this message]
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=CAFCwf10kNLNbeb0g8_Aujup+jAdBPGwyKODTc53iK+N0dKCJNQ@mail.gmail.com \
--to=oded.gabbay@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).