From: Wolfgang Grandegger <wg@grandegger.com>
To: "Andrejus Falčikas" <andrejus.f@8devices.com>,
"Michal Sojka" <michal.sojka@cvut.cz>
Cc: socketcan@hartkopp.net, linux-can@vger.kernel.org
Subject: Re: Fwd: usb_8dev - WARN_ON(in_irq()) Ticket #00560
Date: Thu, 9 Apr 2020 12:25:54 +0200 [thread overview]
Message-ID: <44255c9f-9c22-7bbf-4426-34506bf8a2b0@grandegger.com> (raw)
In-Reply-To: <CAFnz-BUVcSwN6tFUS6W3Y9HUKsbf5am2x=BccSXzX-pRSh9G6w@mail.gmail.com>
Am 09.04.20 um 08:46 schrieb Andrejus Falčikas:
> Hello,
>
> this Ticket #00560 is closed.
Which does not mean that the problem is gone ;)
Wolfgang
> On Fri, Apr 3, 2020 at 4:53 PM Michal Sojka <michal.sojka@cvut.cz> wrote:
>>
>> Hello Wolfgang,
>>
>> On Fri, Apr 03 2020, Wolfgang Grandegger wrote:
>>> Hello Andrejus,
>>>
>>> please do not remove the history of this conversation! It's very
>>> difficult to follow what you are speaking about...
>>>
>>> Am 03.04.20 um 15:04 schrieb Andrejus Falčikas:
>>>> Hello Mr. Oliver Hartkopp,
>>>>
>>>> I would like to notify you that the case described as the issue is
>>>> caused by non-standard use of the device and protocol.
>>
>> [...]
>>
>>>
>>> I observe a similar problem with the GS_USB CAN controller and I have
>>> posted a patch recently here:
>>>
>>> https://marc.info/?l=linux-can&m=158504888512764&w=2
>>>
>>> Could you please give the patch for your device below a try:
>>
>> It would be great if Andrejus can try the patch. If not, I'll try it
>> after I get back to work where I have the device. Unfortunately, due to
>> current situation, I'm not sure when it will happen.
>>
>> Thanks.
>> -Michal
>
>
next prev parent reply other threads:[~2020-04-09 10:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 13:04 Fwd: usb_8dev - WARN_ON(in_irq()) Ticket #00560 Andrejus Falčikas
2020-04-03 13:26 ` Wolfgang Grandegger
2020-04-03 13:53 ` Michal Sojka
2020-04-09 6:46 ` Andrejus Falčikas
2020-04-09 10:25 ` Wolfgang Grandegger [this message]
2020-04-09 10:37 ` Andrejus Falčikas
2020-04-09 10:43 ` Wolfgang Grandegger
2020-04-09 13:00 ` Andrejus Falčikas
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=44255c9f-9c22-7bbf-4426-34506bf8a2b0@grandegger.com \
--to=wg@grandegger.com \
--cc=andrejus.f@8devices.com \
--cc=linux-can@vger.kernel.org \
--cc=michal.sojka@cvut.cz \
--cc=socketcan@hartkopp.net \
/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.