All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Jander <david@protonic.nl>
To: Casper Andersson <casper.casan@gmail.com>
Cc: Vincent Whitchurch <vincent.whitchurch@axis.com>,
	Mark Brown <broonie@kernel.org>,
	linux-spi@vger.kernel.org, Marc Kleine-Budde <mkl@pengutronix.de>,
	Andrew Lunn <andrew@lunn.ch>,
	Lars Povlsen <lars.povlsen@microchip.com>,
	Steen Hegelund <steen.hegelund@microchip.com>,
	Microchip Linux Driver Support <UNGLinuxDriver@microchip.com>
Subject: Re: [PROBLEM] spi driver internal error during boot on sparx5
Date: Fri, 2 Sep 2022 08:38:09 +0200	[thread overview]
Message-ID: <20220902083809.1e41862b@erd992> (raw)
In-Reply-To: <20220901151654.naqa32vckuzvuoac@wse-c0155>

On Thu, 1 Sep 2022 17:16:54 +0200
Casper Andersson <casper.casan@gmail.com> wrote:

> Thanks for the help and fixes. I did some testing with your patches. I
> saw you already submitted the patches, but for reference here's my
> results.
> 
> David's initial fix (changing async->sync):
> no issues
>
> Mark's fix:
> no issues
> 
> David's second fix:
> Issue still occurs. But does not cause any problems and together with
> Mark's fix it works fine.

Thanks a lot for reporting. Happy to know it worked.

Best regards,

-- 
David Jander

  reply	other threads:[~2022-09-02  6:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-26  9:41 [PROBLEM] spi driver internal error during boot on sparx5 Casper Andersson
2022-08-29  8:56 ` David Jander
2022-08-31 16:07   ` Mark Brown
2022-09-01  6:57     ` Vincent Whitchurch
2022-09-01 11:02       ` David Jander
2022-09-01 11:42         ` Vincent Whitchurch
2022-09-01 12:08           ` David Jander
2022-09-01 11:51         ` Mark Brown
2022-09-01 15:16         ` Casper Andersson
2022-09-02  6:38           ` David Jander [this message]
2022-09-01 11:11       ` Mark Brown

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=20220902083809.1e41862b@erd992 \
    --to=david@protonic.nl \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=broonie@kernel.org \
    --cc=casper.casan@gmail.com \
    --cc=lars.povlsen@microchip.com \
    --cc=linux-spi@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=steen.hegelund@microchip.com \
    --cc=vincent.whitchurch@axis.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.