All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Sojka <michal.sojka@cvut.cz>
To: "Wolfgang Grandegger" <wg@grandegger.com>,
	"Andrejus Falčikas" <andrejus.f@8devices.com>,
	socketcan@hartkopp.net
Cc: linux-can@vger.kernel.org
Subject: Re: Fwd: usb_8dev - WARN_ON(in_irq()) Ticket #00560
Date: Fri, 03 Apr 2020 15:53:07 +0200	[thread overview]
Message-ID: <871rp4he0s.fsf@steelpick.2x.cz> (raw)
In-Reply-To: <f17f8d95-96b4-4d51-4390-1fb6a1e47fc8@grandegger.com>

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

  reply	other threads:[~2020-04-03 13:58 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 [this message]
2020-04-09  6:46     ` Andrejus Falčikas
2020-04-09 10:25       ` Wolfgang Grandegger
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=871rp4he0s.fsf@steelpick.2x.cz \
    --to=michal.sojka@cvut.cz \
    --cc=andrejus.f@8devices.com \
    --cc=linux-can@vger.kernel.org \
    --cc=socketcan@hartkopp.net \
    --cc=wg@grandegger.com \
    /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.