On Wed, Jun 23, 2021 at 05:49:55PM -0400, Felix Kuehling wrote:
>
> I can think of two ways to test the changes for MEMORY_DEVICE_GENERIC in
> this patch series in a way that is reproducible without special hardware and
> firmware:
>
> For the reference counting changes we could use the dax drive
On Fri, Oct 04, 2019 at 06:18:04PM -0700, Brendan Higgins wrote:
> > Let's talk about current state. Right now kunit is in linux-next and
> > we want to add a few more tests. We will have to coordinate the effort.
> > Once kunit get into mainline, then the need for this coordination goes
> > down.
On Fri, Oct 04, 2019 at 04:47:09PM -0600, shuah wrote:
> > However, if I encourage arbitrary tests/improvements into my KUnit
> > branch, it further diverges away from torvalds/master, and is more
> > likely that there will be a merge conflict or issue that is not related
> > to the core KUnit chan
On Mon, Sep 23, 2019 at 02:02:30AM -0700, Brendan Higgins wrote:
> ## TL;DR
>
> This revision addresses comments from Linus[1] and Randy[2], by moving
> top level `kunit/` directory to `lib/kunit/` and likewise moves top
> level Kconfig entry under lib/Kconfig.debug, so the KUnit submenu now
> sho
Reviewed-by: Yan Zhao
> -Original Message-
> From: intel-gvt-dev [mailto:intel-gvt-dev-boun...@lists.freedesktop.org] On
> Behalf Of Zhenyu Wang
> Sent: Wednesday, June 12, 2019 11:23 AM
> To: Hariprasad Kelam
> Cc: David Airlie ; intel-...@lists.freedesktop.org; Joonas
> Lahtinen ; linu
Hi lars:
thks for your review, I will move it to hdmi audio driver, give the codec_name
& codec_dai_name an const string.
Best Regards.
Yang KuanKuan | Software Engineer | 15060416783 | ykk at rock-chips.com
From: Lars-Peter Clausen
Date: 2014-12-15 17:02
To: Yakir Yang
CC: Heiko Stuebner; Ro
From: Zhaowei Yuan
If user uses wrong ioctl command with _IOC_NONE and argument size
greater than 0, it can cause NULL pointer access from memset of line
463. If _IOC_NONE, don't memset to 0 for kdata.
Signed-off-by: Zhaowei Yuan
---
drivers/gpu/drm/drm_drv.c |3 ++-
1 file changed, 2 inse
Hi,
I want to unsubscribe from the mailing list.
Thanks,
Hyma
CAUTION - Disclaimer *
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely
for the use of the addressee(s). If you are not the intended recipient, please
notify the sender by
Hi,
I want to unsubscribe from the mailing list.
Thanks,
Hyma
CAUTION - Disclaimer *
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely
for the use of the addressee(s). If you are not the intended recipient, please
notify the sender by e
From: Shirish S
The current logic for probing ddc is limited to
2 blocks (256 bytes), this patch adds support
for the 4 block (512) data.
To do this, a single 8-bit segment index is
passed to the display via the I2C address 30h.
Data from the selected segment is then immediately
read via the reg
From: Shirish S
This patch adds support in probing 4 block edid data, for E-DDC.
This is the first test case in CTS, for HDMI compliance.
Changes from V1:
1. Data type of offset adress updated to unsigned short
2. Updated the buf feild of msg[0]
Changes from V2:
Add switch for DDC and E-DDC
Ch
From: Shirish S
The current logic for probing ddc is limited to
2 blocks (256 bytes), this patch adds support
for the 4 block (512) data.
To do this, a single 8-bit segment index is
passed to the display via the I2C address 30h.
Data from the selected segment is then immediately
read via the reg
From: Shirish S
This patch adds support in probing 4 block edid data, for E-DDC.
This is the first test case in CTS, for HDMI compliance.
Changes from V1:
1. Data type of offset adress updated to unsigned short
2. Updated the buf feild of msg[0]
Changes from V2:
Add switch for DDC and E-DDC
Ch
From: Shirish S
The current logic for probing ddc is limited to
2 blocks (256 bytes), this patch adds support
for the 4 block (512) data.
To do this, a single 8-bit segment index is
passed to the display via the I2C address 30h.
Data from the selected segment is then immediately
read via the reg
From: Shirish S
The current logic for probing ddc is limited to
2 blocks (256 bytes), this patch adds support
for the 4 block (512) data.
To do this, a single 8-bit segment index is
passed to the display via the I2C address 30h.
Data from the selected segment is then immediately
read via the reg
From: Shirish S
This patch adds support in probing 4 block edid data, for E-DDC.
This is the first test case in CTS, for HDMI compliance.
Changes from V1:
1. Data type of offset adress updated to unsigned short
2. Updated the buf feild of msg[0]
Changes from V2:
Add switch for DDC and E-DDC
Ch
From: Shirish S
This patch adds support in probing 4 block edid data, for E-DDC.
This is the first test case in CTS, for HDMI compliance.
Changes from V1:
1. Data type of offset adress updated to unsigned short
2. Updated the buf feild of msg[0]
Changes from V2:
Add switch for DDC and E-DDC
Ch
From: Yufeng Shen
Moved gmbus_mutex below intel_gmbus and added comments.
Rebased to drm-intel-next-queued.
GMBUS has several ports and each has it's own corresponding
I2C adpater. When multiple I2C adapters call gmbus_xfer() at
t
From: Yufeng Shen
Moved gmbus_mutex below intel_gmbus and added comments.
Rebased to drm-intel-next-queued.
GMBUS has several ports and each has it's own corresponding
I2C adpater. When multiple I2C adapters call gmbus_xfer() at
t
On Wed, Jul 21, 2010 at 1:29 AM, Alex Deucher wrote:
> On Tue, Jul 20, 2010 at 5:07 PM, Alexander Y. Fomichev
> wrote:
>> On Wed, Jul 21, 2010 at 1:00 AM, Alex Deucher
>> wrote:
>>> On Tue, Jul 20, 2010 at 4:13 PM, Alexander Y. Fomichev
>>> wrote:
>&g
On Wed, Jul 21, 2010 at 1:00 AM, Alex Deucher wrote:
> On Tue, Jul 20, 2010 at 4:13 PM, Alexander Y. Fomichev
> wrote:
>> On Tue, Jul 20, 2010 at 9:37 PM, Alex Deucher
>> wrote:
>>> On Mon, Jul 19, 2010 at 5:42 PM, Alexander Y. Fomichev
>>> wrote:
>&
On Tue, Jul 20, 2010 at 9:37 PM, Alex Deucher wrote:
> On Mon, Jul 19, 2010 at 5:42 PM, Alexander Y. Fomichev
> wrote:
>> This patch fix possible NULL pointer dereference when
>> r600_prepare_blit_copy tries to fill dev_priv->blit_vb->file_priv
>> without check
On Wed, Jul 21, 2010 at 1:29 AM, Alex Deucher wrote:
> On Tue, Jul 20, 2010 at 5:07 PM, Alexander Y. Fomichev
> wrote:
>> On Wed, Jul 21, 2010 at 1:00 AM, Alex Deucher wrote:
>>> On Tue, Jul 20, 2010 at 4:13 PM, Alexander Y. Fomichev
>>> wrote:
>>>
On Wed, Jul 21, 2010 at 1:00 AM, Alex Deucher wrote:
> On Tue, Jul 20, 2010 at 4:13 PM, Alexander Y. Fomichev
> wrote:
>> On Tue, Jul 20, 2010 at 9:37 PM, Alex Deucher wrote:
>>> On Mon, Jul 19, 2010 at 5:42 PM, Alexander Y. Fomichev
>>> wrote:
>>>
On Tue, Jul 20, 2010 at 9:37 PM, Alex Deucher wrote:
> On Mon, Jul 19, 2010 at 5:42 PM, Alexander Y. Fomichev
> wrote:
>> This patch fix possible NULL pointer dereference when
>> r600_prepare_blit_copy tries to fill dev_priv->blit_vb->file_priv
>> without check
This patch fix possible NULL pointer dereference when
r600_prepare_blit_copy tries to fill dev_priv->blit_vb->file_priv
without check of dev_priv->blit_vb. dev_priv->blit_vb should be
filled by r600_nomm_get_vb but latest can fail with EAGAIN.
Addresses: https://bugzilla.kernel.org/show_bug.cgi?id=
This patch fix possible NULL pointer dereference when
r600_prepare_blit_copy tries to fill dev_priv->blit_vb->file_priv
without check of dev_priv->blit_vb. dev_priv->blit_vb should be
filled by r600_nomm_get_vb but latest can fail with EAGAIN.
Addresses: https://bugzilla.kernel.org/show_bug.cgi?id=
27 matches
Mail list logo
