From: Greg KH <gregkh@linuxfoundation.org>
To: Oded Gabbay <ogabbay@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [git pull] habanalabs pull request for kernel 5.19
Date: Sat, 21 May 2022 15:22:41 +0200 [thread overview]
Message-ID: <Yojnof1ekJg3yjwu@kroah.com> (raw)
In-Reply-To: <20220521115325.GA1965670@ogabbay-vm-u20.habana-labs.com>
On Sat, May 21, 2022 at 02:53:25PM +0300, Oded Gabbay wrote:
> Hi Greg,
>
> This is habanalabs pull request for the merge window of kernel 5.19.
> We added a few minor features, such as support eventfd registration
> for device events, and the ability to scrub the device memory
> through debugfs.
>
> We did some refactoring such as adding a centralized memory
> manager inside the driver for allocating mmapable memory and tracking
> it, so we can remove different code paths that basically duplicated
> that functionality.
>
> And, as usual, there are multiple bug fixes.
>
> Full details are in the tag.
>
> Thanks,
> Oded
>
> The following changes since commit cafada1fe932ce761d6c0bc1d56967e27abe4cff:
>
> Revert "speakup: Generate speakupmap.h automatically" (2022-05-20 21:07:05 +0200)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/ogabbay/linux.git tags/misc-habanalabs-next-2022-05-21
>
> for you to fetch changes up to 93f742b13260b070a695f44d6b6ff696cb5cbcd8:
>
> habanalabs: use separate structure info for each error collect data (2022-05-21 14:42:17 +0300)
Has this been in linux-next already? It's _really_ late to be adding
new commits to my trees as 5.17 is about to come out in a few hours :(
greg k-h
next prev parent reply other threads:[~2022-05-21 13:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-21 11:53 [git pull] habanalabs pull request for kernel 5.19 Oded Gabbay
2022-05-21 13:22 ` Greg KH [this message]
2022-05-21 14:53 ` Oded Gabbay
2022-05-21 18:21 ` Greg KH
2022-05-21 21:07 ` Oded Gabbay
2022-05-22 19:09 ` Greg KH
2022-05-22 19:35 ` 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=Yojnof1ekJg3yjwu@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ogabbay@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