From: Andi Shyti <andi.shyti@linux.intel.com>
To: Anusha Srivatsa <anusha.srivatsa@intel.com>
Cc: intel-gfx@lists.freedesktop.org,
Lucas De Marchi <lucas.demarchi@intel.com>,
stable@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/dmc: Add MMIO range restrictions
Date: Wed, 27 Apr 2022 14:42:08 +0200 [thread overview]
Message-ID: <Ymk6ICgcRio8zE4g@intel.intel> (raw)
In-Reply-To: <20220427003509.267683-1-anusha.srivatsa@intel.com>
[...]
> + if (!dmc_mmio_addr_sanity_check(dmc, mmioaddr, mmio_count, dmc_header->header_ver, dmc_id))
> + drm_err(&i915->drm, "DMC firmware has Wrong MMIO Addresses\n");
> + return 0;
> +
mh? :)
next prev parent reply other threads:[~2022-04-27 12:42 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 0:35 [Intel-gfx] [PATCH] drm/i915/dmc: Add MMIO range restrictions Anusha Srivatsa
2022-04-27 0:35 ` Anusha Srivatsa
2022-04-27 1:44 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/dmc: Add MMIO range restrictions (rev3) Patchwork
2022-04-27 2:10 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-04-27 4:26 ` [Intel-gfx] [PATCH] drm/i915/dmc: Add MMIO range restrictions kernel test robot
2022-04-27 4:26 ` kernel test robot
2022-04-27 5:41 ` Lucas De Marchi
2022-04-27 5:41 ` Lucas De Marchi
2022-04-29 20:39 ` [Intel-gfx] " Srivatsa, Anusha
2022-04-29 20:39 ` Srivatsa, Anusha
2022-04-29 20:49 ` [Intel-gfx] " Lucas De Marchi
2022-04-29 20:49 ` Lucas De Marchi
2022-04-29 22:57 ` [Intel-gfx] " Srivatsa, Anusha
2022-04-29 22:57 ` Srivatsa, Anusha
2022-05-02 18:09 ` [Intel-gfx] " Lucas De Marchi
2022-04-27 7:49 ` kernel test robot
2022-04-27 7:49 ` kernel test robot
2022-04-27 12:42 ` Andi Shyti [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-06 17:35 Anusha Srivatsa
2022-05-04 18:32 Anusha Srivatsa
2022-05-04 0:13 Anusha Srivatsa
2022-05-04 0:31 ` Lucas De Marchi
2022-05-04 0:36 ` Srivatsa, Anusha
2022-05-03 23:36 Anusha Srivatsa
2022-05-03 22:04 Anusha Srivatsa
2022-04-05 17:14 Anusha Srivatsa
2022-04-05 18:02 ` Lucas De Marchi
2022-04-06 17:16 ` Srivatsa, Anusha
2022-04-06 17:46 ` Lucas De Marchi
2022-04-06 20:53 ` Srivatsa, Anusha
2022-04-25 18:16 ` Lucas De Marchi
2022-04-05 23:18 ` kernel test robot
2022-04-06 6:58 ` kernel test robot
2022-04-05 0:35 Anusha Srivatsa
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=Ymk6ICgcRio8zE4g@intel.intel \
--to=andi.shyti@linux.intel.com \
--cc=anusha.srivatsa@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=stable@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 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.