All of lore.kernel.org
 help / color / mirror / Atom feed
From: fuyao <fuyao1697@cyg.com>
To: Evgeny Boger <boger@wirenboard.com>
Cc: devicetree@vger.kernel.org, jernej.skrabec@gmail.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-sunxi@lists.linux.dev,
	maijianzhang@allwinnertech.com, mripard@kernel.org,
	robh+dt@kernel.org, wens@csie.org
Subject: Re: [PATCH] sunxi:dts: remove r40 can node
Date: Mon, 14 Mar 2022 09:58:14 +0800	[thread overview]
Message-ID: <Yi6hNkerDE0oyilv@scg> (raw)
In-Reply-To: <bc846d95-5571-cfd1-c848-1ae9240f50a4@wirenboard.com>

On Wed, Mar 09, 2022 at 02:44:56AM +0300, Evgeny Boger wrote:
> Hi,
> 
> as I explained in the original commit message, CAN is definitely there and
> is working perfectly at least on A40i.
> I know it was removed from the user manual, but I personally verified that
> it is working.
sorry, I forgot read the commit msg;
> 
> Maybe you can tell why CAN should be removed besides not being described in
> the manual? Are there some hardware or maybe license issues?

i will test it again. 

thanks!

> 
> Thanks!
> 
> --
>  Best wishes,
>  Evgeny Boger
>  CTO @ wirenboard.com
> 
> 
> 
> 

-- 
Technology is exciting


WARNING: multiple messages have this Message-ID (diff)
From: fuyao <fuyao1697@cyg.com>
To: Evgeny Boger <boger@wirenboard.com>
Cc: devicetree@vger.kernel.org, jernej.skrabec@gmail.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-sunxi@lists.linux.dev,
	maijianzhang@allwinnertech.com, mripard@kernel.org,
	robh+dt@kernel.org, wens@csie.org
Subject: Re: [PATCH] sunxi:dts: remove r40 can node
Date: Mon, 14 Mar 2022 09:58:14 +0800	[thread overview]
Message-ID: <Yi6hNkerDE0oyilv@scg> (raw)
In-Reply-To: <bc846d95-5571-cfd1-c848-1ae9240f50a4@wirenboard.com>

On Wed, Mar 09, 2022 at 02:44:56AM +0300, Evgeny Boger wrote:
> Hi,
> 
> as I explained in the original commit message, CAN is definitely there and
> is working perfectly at least on A40i.
> I know it was removed from the user manual, but I personally verified that
> it is working.
sorry, I forgot read the commit msg;
> 
> Maybe you can tell why CAN should be removed besides not being described in
> the manual? Are there some hardware or maybe license issues?

i will test it again. 

thanks!

> 
> Thanks!
> 
> --
>  Best wishes,
>  Evgeny Boger
>  CTO @ wirenboard.com
> 
> 
> 
> 

-- 
Technology is exciting


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-03-14  2:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-03 11:32 [PATCH] sunxi:dts: remove r40 can node fuyao
2022-03-03 11:32 ` fuyao
2022-03-08 23:44 ` Evgeny Boger
2022-03-08 23:44   ` Evgeny Boger
2022-03-14  1:58   ` fuyao [this message]
2022-03-14  1:58     ` fuyao
  -- strict thread matches above, loose matches on Subject: below --
2022-03-03 11:21 fuyao
2022-03-03 11:21 ` fuyao

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=Yi6hNkerDE0oyilv@scg \
    --to=fuyao1697@cyg.com \
    --cc=boger@wirenboard.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=maijianzhang@allwinnertech.com \
    --cc=mripard@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=wens@csie.org \
    /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.