All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Joshua Quesenberry" <engnfrc@gmail.com>
To: "'Patrick Menschel'" <menschel.p@posteo.de>,
	"'Marc Kleine-Budde'" <mkl@pengutronix.de>
Cc: <kernel@pengutronix.de>, <linux-can@vger.kernel.org>,
	<engnfrc@gmail.com>
Subject: RE: MCP2518FD Drivers Rarely Working with Custom Kernel 5.10.Y
Date: Mon, 12 Jul 2021 16:01:28 -0400	[thread overview]
Message-ID: <02dd01d77758$b3c79d70$1b56d850$@gmail.com> (raw)
In-Reply-To: <d68ced7f-a407-da41-520f-d12d8161f027@posteo.de>

Thanks for the suggestion Patrick! I will do that shortly.

Josh Q

-----Original Message-----
From: Patrick Menschel <menschel.p@posteo.de> 
Sent: Monday, July 12, 2021 3:57 PM
To: Joshua Quesenberry <engnfrc@gmail.com>; 'Marc Kleine-Budde' <mkl@pengutronix.de>
Cc: kernel@pengutronix.de; linux-can@vger.kernel.org
Subject: Re: MCP2518FD Drivers Rarely Working with Custom Kernel 5.10.Y

Am 12.07.21 um 20:57 schrieb Joshua Quesenberry:
> Any thoughts on my recent findings? So far the raspberrypi.org forums haven't proved fruitful, not sure if there's another more appropriate place I should take this conversation now that the issue doesn't seem to be relating to the CAN drivers themselves, but underlying subsystems conflicting.


Technically you could open an issue on
https://github.com/raspberrypi/linux

This is usually the straight forward solution to get in touch with the platform experts.

Cheers,
Patrick


      reply	other threads:[~2021-07-12 20:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <016701d7678c$2b3d50c0$81b7f240$@gmail.com>
     [not found] ` <20210622212818.enfx5fzgghfxfznb@pengutronix.de>
2021-06-23  2:59   ` MCP2518FD Drivers Rarely Working with Custom Kernel 5.10.Y Joshua Quesenberry
2021-06-23  5:24     ` Patrick Menschel
2021-06-23 17:34       ` Joshua Quesenberry
2021-06-23 20:07         ` Patrick Menschel
2021-06-24 18:24           ` Joshua Quesenberry
2021-06-24 20:41             ` Patrick Menschel
2021-06-25  6:56         ` Marc Kleine-Budde
2021-06-25 12:16           ` Marc Kleine-Budde
     [not found]             ` <020f01d769da$9fac86b0$df059410$@gmail.com>
     [not found]               ` <022d01d769e2$e623cbf0$b26b63d0$@gmail.com>
2021-07-02  4:33                 ` Joshua Quesenberry
2021-07-02  9:31                 ` Marc Kleine-Budde
2021-07-02 14:26                   ` Joshua Quesenberry
2021-07-06 18:40                     ` Joshua Quesenberry
2021-07-12 18:57                       ` Joshua Quesenberry
2021-07-12 19:56                         ` Patrick Menschel
2021-07-12 20:01                           ` Joshua Quesenberry [this message]

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='02dd01d77758$b3c79d70$1b56d850$@gmail.com' \
    --to=engnfrc@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-can@vger.kernel.org \
    --cc=menschel.p@posteo.de \
    --cc=mkl@pengutronix.de \
    /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.