From: Tomer Tayar <ttayar@habana.ai>
To: Oded Gabbay <oded.gabbay@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Omer Shpigelman <oshpigelman@habana.ai>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Subject: RE: [PATCH 2/2] habanalabs: update F/W register map
Date: Tue, 28 Apr 2020 05:44:16 +0000 [thread overview]
Message-ID: <DB8PR02MB54686EF2DB22033260E5F6E2D2AC0@DB8PR02MB5468.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <20200427234047.13249-2-oded.gabbay@gmail.com>
On Tue, Apr 28, 2020 at 2:41 AM, Oded Gabbay <oded.gabbay@gmail.com> wrote:
> Update the mapping to the latest one used by the Firmware. No impact on
> the driver in this update.
>
> Signed-off-by: Oded Gabbay <oded.gabbay@gmail.com>
Reviewed-by: Tomer Tayar <ttayar@habana.ai>
prev parent reply other threads:[~2020-04-28 5:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 23:40 [PATCH 1/2] habanalabs: enable trace data compression (profiler) Oded Gabbay
2020-04-27 23:40 ` [PATCH 2/2] habanalabs: update F/W register map Oded Gabbay
2020-04-28 5:44 ` Tomer Tayar [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=DB8PR02MB54686EF2DB22033260E5F6E2D2AC0@DB8PR02MB5468.eurprd02.prod.outlook.com \
--to=ttayar@habana.ai \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oded.gabbay@gmail.com \
--cc=oshpigelman@habana.ai \
/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).