linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Zong-Zhe Yang <kevin_yang@realtek.com>
Subject: Re: [PATCH 1/2] wifi: rtw88: select WANT_DEV_COREDUMP
Date: Wed, 31 Jul 2024 11:39:13 +0300	[thread overview]
Message-ID: <87jzh2klam.fsf@kernel.org> (raw)
In-Reply-To: <5db66445dbd1454ea6c2a6f8fc664725@realtek.com> (Ping-Ke Shih's message of "Wed, 31 Jul 2024 00:38:09 +0000")

Ping-Ke Shih <pkshih@realtek.com> writes:

> Kalle Valo <kvalo@kernel.org> wrote:
>> Ping-Ke Shih <pkshih@realtek.com> writes:
>> 
>> > From: Zong-Zhe Yang <kevin_yang@realtek.com>
>> >
>> > We have invoked device coredump when fw crash.
>> > Should select WANT_DEV_COREDUMP by ourselves.
>> >
>> > Signed-off-by: Zong-Zhe Yang <kevin_yang@realtek.com>
>> > Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
>> 
>> Should these two go to wireless tree? If yes, please assign the patches
>> to me on patchwork. But rtw tree is fine for me as well, your call.
>
> For most distro, other drivers select this flag, so not urgent to have these
> two patches. Then they will go via rtw tree. Thanks. 

Makes sense, thanks.

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

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

  reply	other threads:[~2024-07-31  8:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-18  7:06 [PATCH 1/2] wifi: rtw88: select WANT_DEV_COREDUMP Ping-Ke Shih
2024-07-18  7:06 ` [PATCH 2/2] wifi: rtw89: " Ping-Ke Shih
2024-07-30 13:08 ` [PATCH 1/2] wifi: rtw88: " Kalle Valo
2024-07-31  0:38   ` Ping-Ke Shih
2024-07-31  8:39     ` Kalle Valo [this message]
2024-07-31  5:46 ` Ping-Ke Shih

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=87jzh2klam.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=kevin_yang@realtek.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@realtek.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).