All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Stephen Boyd <swboyd@chromium.org>
Cc: pillair@codeaurora.org, ath10k@lists.infradead.org,
	govinds@codeaurora.org, kuabhs@chromium.org,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	youghand@codeaurora.org
Subject: Re: [PATCH] ath10k: Don't always treat modem stop events as crashes
Date: Fri, 24 Sep 2021 10:59:47 +0300	[thread overview]
Message-ID: <87bl4itnd8.fsf@codeaurora.org> (raw)
In-Reply-To: <CAE-0n52DcCwcdR07fvMLrj=RJFtNthy0FdWmt1gBWiD9eLrOvQ@mail.gmail.com> (Stephen Boyd's message of "Wed, 22 Sep 2021 15:20:07 -0700")

Stephen Boyd <swboyd@chromium.org> writes:

> Quoting pillair@codeaurora.org (2021-09-21 22:35:34)
>> On 9/5/21 4:04 PM, Stephen Boyd wrote:
>>
>> > +static int ath10k_snoc_modem_notify(struct notifier_block *nb, unsigned long
> [...]
>>
>> > +
>>
>> > +          return NOTIFY_OK;
>>
>> > +}
>>
>>
>>
>> Thanks for posting the patch. It would be preferable to use a different flag
>> instead of ATH10K_SNOC_FLAG_UNREGISTERING,
>>
>> since we are not unloading the ath10k driver.

Weird, I don't see pillair's email on patchwork[1] and not in the ath10k
list either. Was it sent as HTML or something?

[1] https://patchwork.kernel.org/project/linux-wireless/patch/20210905210400.1157870-1-swboyd@chromium.org/

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

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

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@codeaurora.org>
To: Stephen Boyd <swboyd@chromium.org>
Cc: pillair@codeaurora.org, ath10k@lists.infradead.org,
	govinds@codeaurora.org, kuabhs@chromium.org,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	youghand@codeaurora.org
Subject: Re: [PATCH] ath10k: Don't always treat modem stop events as crashes
Date: Fri, 24 Sep 2021 10:59:47 +0300	[thread overview]
Message-ID: <87bl4itnd8.fsf@codeaurora.org> (raw)
In-Reply-To: <CAE-0n52DcCwcdR07fvMLrj=RJFtNthy0FdWmt1gBWiD9eLrOvQ@mail.gmail.com> (Stephen Boyd's message of "Wed, 22 Sep 2021 15:20:07 -0700")

Stephen Boyd <swboyd@chromium.org> writes:

> Quoting pillair@codeaurora.org (2021-09-21 22:35:34)
>> On 9/5/21 4:04 PM, Stephen Boyd wrote:
>>
>> > +static int ath10k_snoc_modem_notify(struct notifier_block *nb, unsigned long
> [...]
>>
>> > +
>>
>> > +          return NOTIFY_OK;
>>
>> > +}
>>
>>
>>
>> Thanks for posting the patch. It would be preferable to use a different flag
>> instead of ATH10K_SNOC_FLAG_UNREGISTERING,
>>
>> since we are not unloading the ath10k driver.

Weird, I don't see pillair's email on patchwork[1] and not in the ath10k
list either. Was it sent as HTML or something?

[1] https://patchwork.kernel.org/project/linux-wireless/patch/20210905210400.1157870-1-swboyd@chromium.org/

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

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

  reply	other threads:[~2021-09-24  8:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <002501d7af73$ae0a7620$0a1f6260$@codeaurora.org>
2021-09-22 22:20 ` [PATCH] ath10k: Don't always treat modem stop events as crashes Stephen Boyd
2021-09-22 22:20   ` Stephen Boyd
2021-09-24  7:59   ` Kalle Valo [this message]
2021-09-24  7:59     ` Kalle Valo
2021-09-24  8:07     ` pillair
2021-09-24  8:07       ` pillair
2021-09-05 21:04 Stephen Boyd
2021-09-05 21:04 ` Stephen Boyd
2021-09-06  0:43 ` Steev Klimaszewski
2021-09-06  0:43   ` Steev Klimaszewski
2021-09-07 19:32 ` Matthias Kaehlcke
2021-09-07 19:32   ` Matthias Kaehlcke
2021-09-07 19:48   ` Stephen Boyd
2021-09-07 19:48     ` Stephen Boyd
2021-09-08 22:37     ` Abhishek Kumar
2021-09-08 22:37       ` Abhishek Kumar
2021-09-09  0:21       ` Stephen Boyd
2021-09-09  0:21         ` Stephen Boyd

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=87bl4itnd8.fsf@codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=ath10k@lists.infradead.org \
    --cc=govinds@codeaurora.org \
    --cc=kuabhs@chromium.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pillair@codeaurora.org \
    --cc=swboyd@chromium.org \
    --cc=youghand@codeaurora.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.