On Mon, Jun 12, 2017 at 1:19 PM, Peter Rosin wrote:
> On 2017-06-12 11:38, Andy Shevchenko wrote:
>> On Mon, Jun 12, 2017 at 12:28 PM, Peter Rosin wrote:
>>> On 2017-06-12 11:11, Andy Shevchenko wrote:
On Mon, Jun 12, 2017 at 6:42 AM, Song liwei
On Mon, Jun 12, 2017 at 1:19 PM, Peter Rosin wrote:
> On 2017-06-12 11:38, Andy Shevchenko wrote:
>> On Mon, Jun 12, 2017 at 12:28 PM, Peter Rosin wrote:
>>> On 2017-06-12 11:11, Andy Shevchenko wrote:
On Mon, Jun 12, 2017 at 6:42 AM, Song liwei
wrote:
> From: Liwei Song
>>
On 2017-06-12 11:38, Andy Shevchenko wrote:
> On Mon, Jun 12, 2017 at 12:28 PM, Peter Rosin wrote:
>> On 2017-06-12 11:11, Andy Shevchenko wrote:
>>> On Mon, Jun 12, 2017 at 6:42 AM, Song liwei
>>> wrote:
From: Liwei Song
On 2017-06-12 11:38, Andy Shevchenko wrote:
> On Mon, Jun 12, 2017 at 12:28 PM, Peter Rosin wrote:
>> On 2017-06-12 11:11, Andy Shevchenko wrote:
>>> On Mon, Jun 12, 2017 at 6:42 AM, Song liwei
>>> wrote:
From: Liwei Song
>
After finished I2C block read/write, when unmap the data
On Mon, Jun 12, 2017 at 6:42 AM, Song liwei wrote:
> From: Liwei Song
Btw, it seems it has to include Fixes tag.
> Signed-off-by: Liwei Song
> ---
> drivers/i2c/busses/i2c-ismt.c | 2 +-
> 1 file changed, 1
On Mon, Jun 12, 2017 at 6:42 AM, Song liwei wrote:
> From: Liwei Song
Btw, it seems it has to include Fixes tag.
> Signed-off-by: Liwei Song
> ---
> drivers/i2c/busses/i2c-ismt.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/i2c/busses/i2c-ismt.c
On Mon, Jun 12, 2017 at 12:28 PM, Peter Rosin wrote:
> On 2017-06-12 11:11, Andy Shevchenko wrote:
>> On Mon, Jun 12, 2017 at 6:42 AM, Song liwei wrote:
>>> From: Liwei Song
>>> After finished I2C block read/write, when unmap
On Mon, Jun 12, 2017 at 12:28 PM, Peter Rosin wrote:
> On 2017-06-12 11:11, Andy Shevchenko wrote:
>> On Mon, Jun 12, 2017 at 6:42 AM, Song liwei wrote:
>>> From: Liwei Song
>>> After finished I2C block read/write, when unmap the data buffer,
>>> a wrong device address was pass to
On 2017-06-12 11:11, Andy Shevchenko wrote:
> On Mon, Jun 12, 2017 at 6:42 AM, Song liwei wrote:
>> From: Liwei Song
>>
>
>> Fix the following calltrace:
>
> No, you don't fix a call trace, you are fixing a bug.
>
>> This happen When run
On 2017-06-12 11:11, Andy Shevchenko wrote:
> On Mon, Jun 12, 2017 at 6:42 AM, Song liwei wrote:
>> From: Liwei Song
>>
>
>> Fix the following calltrace:
>
> No, you don't fix a call trace, you are fixing a bug.
>
>> This happen When run "i2cdetect -y 0" detect SMBus iSMT adapter.
>>
>> After
On Mon, Jun 12, 2017 at 6:42 AM, Song liwei wrote:
> From: Liwei Song
>
> Fix the following calltrace:
No, you don't fix a call trace, you are fixing a bug.
> This happen When run "i2cdetect -y 0" detect SMBus iSMT adapter.
>
> After
On Mon, Jun 12, 2017 at 6:42 AM, Song liwei wrote:
> From: Liwei Song
>
> Fix the following calltrace:
No, you don't fix a call trace, you are fixing a bug.
> This happen When run "i2cdetect -y 0" detect SMBus iSMT adapter.
>
> After finished I2C block read/write, when unmap the data buffer,
From: Liwei Song
Fix the following calltrace:
kernel BUG at drivers/iommu/intel-iommu.c:3260!
invalid opcode: [#5] PREEMPT SMP
Hardware name: Intel Corp. Harcuvar/Server, BIOS
HAVLCRB0.X64.0013.D39.1608311820 08/31/2016
task: 880175389950 ti: 880176bec000
From: Liwei Song
Fix the following calltrace:
kernel BUG at drivers/iommu/intel-iommu.c:3260!
invalid opcode: [#5] PREEMPT SMP
Hardware name: Intel Corp. Harcuvar/Server, BIOS
HAVLCRB0.X64.0013.D39.1608311820 08/31/2016
task: 880175389950 ti: 880176bec000 task.ti: 880176bec000
14 matches
Mail list logo