From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Cc: linux-can@vger.kernel.org, Chee Hou Ong <chee.houx.ong@intel.com>,
Aman Kumar <aman.kumar@intel.com>,
Pallavi Kumari <kumari.pallavi@intel.com>,
Tomoya MORINAGA <tomoya-linux@dsn.okisemi.com>,
Masayuki Ohtake <masa-korg@dsn.okisemi.com>
Subject: Re: PCH_CAN removal?
Date: Fri, 20 May 2022 16:24:39 +0200 [thread overview]
Message-ID: <0cb33596-dd1d-4536-a0c3-50f3592ca8c7@hartkopp.net> (raw)
In-Reply-To: <29930b66-d02e-411a-d6f5-4f09119f3f1e@linux.intel.com>
Hi Jarkko,
thanks for your fast reply!
On 20.05.22 14:48, Jarkko Nikula wrote:
> On 5/19/22 22:15, Oliver Hartkopp wrote:
>> As I do not have that hardware anymore it would be interesting to see
>> if you could bring the PCH board to life with the C_CAN_PCI driver?!?
>>
>> That would allow us to remove the (then definitely) obsolete pch_can
>> driver.
>>
> I'm afraid we don't have that HW either here locally :-(
Hm, sad. At least it was a try to get the pch_can removed ;-)
Many thanks & best regards,
Oliver
ps. to whom it may concern: the two mail addresses from the OKISEMI
employees bounced at sending :-[
next prev parent reply other threads:[~2022-05-20 14:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 13:08 [PATCH net 0/2] pull-request: can 2022-05-13 Marc Kleine-Budde
2022-05-13 13:08 ` [PATCH net 1/2] Revert "can: m_can: pci: use custom bit timings for Elkhart Lake" Marc Kleine-Budde
2022-05-13 17:21 ` Jakub Kicinski
2022-05-14 19:00 ` Marc Kleine-Budde
2022-05-18 12:47 ` Jarkko Nikula
2022-05-19 19:15 ` PCH_CAN removal? Oliver Hartkopp
2022-05-20 12:48 ` Jarkko Nikula
2022-05-20 14:24 ` Oliver Hartkopp [this message]
2022-05-13 13:08 ` [PATCH net 2/2] can: m_can: remove support for custom bit timing, take #2 Marc Kleine-Budde
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=0cb33596-dd1d-4536-a0c3-50f3592ca8c7@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=aman.kumar@intel.com \
--cc=chee.houx.ong@intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=kumari.pallavi@intel.com \
--cc=linux-can@vger.kernel.org \
--cc=masa-korg@dsn.okisemi.com \
--cc=tomoya-linux@dsn.okisemi.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.