From: "Tim Jiang (QUIC)" <quic_tjiang@quicinc.com>
To: "dmitry.baryshkov@linaro.org" <dmitry.baryshkov@linaro.org>
Cc: "marcel@holtmann.org" <marcel@holtmann.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"Balakrishna Godavarthi (QUIC)" <quic_bgodavar@quicinc.com>,
"Hemant Gupta (QUIC)" <quic_hemantg@quicinc.com>,
"mka@chromium.org" <mka@chromium.org>
Subject: RE: [PATCH v2] Bluetooth: btusb: Add WCN6855 devcoredump support
Date: Tue, 18 Apr 2023 09:16:43 +0000 [thread overview]
Message-ID: <11d65b0864b142ffb92255318ce70c45@quicinc.com> (raw)
In-Reply-To: <CAA8EJprztGdP0yqV=O6P2tn4i0+iQ4rfBVY2x-3_93o3C0c-Nw@mail.gmail.com>
Hi Dmitry:
> > On Thu, 13 Apr 2023 at 09:44, Tim Jiang <quic_tjiang@quicinc.com> wrote:
> > >
> > > WCN6855 will report memdump via ACL data or HCI event when it get
> > > crashed, so we collect memdump to debug firmware.
> >
> > Is it applicable only to wcn6855 or to some of earlier chips too?
> > [Tim] Also applicable to earlier chips , but currently google only
> > require us to support wcn6855
>
> Since upstream is not a google kernel, please enable this feature for all relevant chipsets.
> [Tim] agreed , but the title of this gerrit unchanged, I raise a new gerrit for other relevant chipsets , is OK?
There is no gerrit here.
Also, is there any chance you can fix your email client to stop putting old headers at the top of the email?
[Tim] sorry for confusion, I mean I will raise another new change for other relevant chipset, is OK ?
and I use office 365 to reply your email which will adding old headers automatically , unless I delete the old headers manually, thank you.
>
> >
> > >
> > > Signed-off-by: Tim Jiang <quic_tjiang@quicinc.com>
> > > ---
> > > drivers/bluetooth/btusb.c | 222
> > > ++++++++++++++++++++++++++++++++++++++
> > > 1 file changed, 222 insertions(+)
>
>
>
>
> --
> With best wishes
> Dmitry
--
With best wishes
Dmitry
next prev parent reply other threads:[~2023-04-18 9:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 6:43 [PATCH v2] Bluetooth: btusb: Add WCN6855 devcoredump support Tim Jiang
2023-04-14 20:57 ` Luiz Augusto von Dentz
2023-04-18 1:02 ` Tim Jiang (QUIC)
2023-04-14 21:02 ` Dmitry Baryshkov
2023-04-18 1:02 ` Tim Jiang (QUIC)
2023-04-18 9:02 ` Dmitry Baryshkov
2023-04-18 9:07 ` Tim Jiang (QUIC)
2023-04-18 9:10 ` Dmitry Baryshkov
2023-04-18 9:16 ` Tim Jiang (QUIC) [this message]
2023-04-18 16:59 ` Dmitry Baryshkov
-- strict thread matches above, loose matches on Subject: below --
2023-04-10 9:53 Tim Jiang
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=11d65b0864b142ffb92255318ce70c45@quicinc.com \
--to=quic_tjiang@quicinc.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mka@chromium.org \
--cc=quic_bgodavar@quicinc.com \
--cc=quic_hemantg@quicinc.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