All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Loic Poulain <loic.poulain@linaro.org>
Cc: kuba@kernel.org, davem@davemloft.net, netdev@vger.kernel.org,
	ath11k@lists.infradead.org, regressions@lists.linux.dev,
	hemantk@codeaurora.org, nschichan@freebox.fr,
	manivannan.sadhasivam@linaro.org
Subject: Re: [PATCH] qrtr: mhi: Fix duplicate channel start
Date: Thu, 26 Aug 2021 19:34:32 +0300	[thread overview]
Message-ID: <87a6l46u7b.fsf@codeaurora.org> (raw)
In-Reply-To: <1629992163-6252-1-git-send-email-loic.poulain@linaro.org> (Loic Poulain's message of "Thu, 26 Aug 2021 17:36:03 +0200")

Loic Poulain <loic.poulain@linaro.org> writes:

> commit ce78ffa3ef16 ("net: really fix the build...") handling a merge
> conflict causes the mhi_prepare_for_transfer() function to be called
> twice (with different flags), leading to QRTR probing issues.
>
> Fixes: ce78ffa3ef16 ("net: really fix the build...")
> Signed-off-by: Loic Poulain <loic.poulain@linaro.org>

Thanks for the patch, but with this patch the whole kernel crashes. I
tested on a NUC box with QCA6390 using v5.14-rc7. Unfortunately no
netconsole at the moment as I'm moving my workstations.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@codeaurora.org>
To: Loic Poulain <loic.poulain@linaro.org>
Cc: kuba@kernel.org,  davem@davemloft.net,  netdev@vger.kernel.org,
	 ath11k@lists.infradead.org,  regressions@lists.linux.dev,
	 hemantk@codeaurora.org,  nschichan@freebox.fr,
	 manivannan.sadhasivam@linaro.org
Subject: Re: [PATCH] qrtr: mhi: Fix duplicate channel start
Date: Thu, 26 Aug 2021 19:34:32 +0300	[thread overview]
Message-ID: <87a6l46u7b.fsf@codeaurora.org> (raw)
In-Reply-To: <1629992163-6252-1-git-send-email-loic.poulain@linaro.org> (Loic Poulain's message of "Thu, 26 Aug 2021 17:36:03 +0200")

Loic Poulain <loic.poulain@linaro.org> writes:

> commit ce78ffa3ef16 ("net: really fix the build...") handling a merge
> conflict causes the mhi_prepare_for_transfer() function to be called
> twice (with different flags), leading to QRTR probing issues.
>
> Fixes: ce78ffa3ef16 ("net: really fix the build...")
> Signed-off-by: Loic Poulain <loic.poulain@linaro.org>

Thanks for the patch, but with this patch the whole kernel crashes. I
tested on a NUC box with QCA6390 using v5.14-rc7. Unfortunately no
netconsole at the moment as I'm moving my workstations.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2021-08-26 16:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-26 15:36 [PATCH] qrtr: mhi: Fix duplicate channel start Loic Poulain
2021-08-26 15:36 ` Loic Poulain
2021-08-26 16:34 ` Kalle Valo [this message]
2021-08-26 16:34   ` Kalle Valo

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=87a6l46u7b.fsf@codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=ath11k@lists.infradead.org \
    --cc=davem@davemloft.net \
    --cc=hemantk@codeaurora.org \
    --cc=kuba@kernel.org \
    --cc=loic.poulain@linaro.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=netdev@vger.kernel.org \
    --cc=nschichan@freebox.fr \
    --cc=regressions@lists.linux.dev \
    /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.