From: Kalle Valo <kvalo@codeaurora.org>
To: Govind Singh <govinds@codeaurora.org>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH] ath10k: update HOST capability qmi message
Date: Wed, 28 Nov 2018 16:00:16 +0200 [thread overview]
Message-ID: <87lg5d715b.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20181119113101.23359-1-govinds@codeaurora.org> (Govind Singh's message of "Mon, 19 Nov 2018 17:01:01 +0530")
Govind Singh <govinds@codeaurora.org> writes:
> HOST capability interface data structures are updated
> in HL3.1 fw version. Update the qmi host capability
> members for compatibility across different firmware
> versions.
> With this change HL2.0 fw upgrade is required as this
> change breaks the backward compatibility with HL2.0 fw.
The last sentence is not making any sense to me, does it have a typo or
am I missing something?
If there's a typo I can fix it, no need to resend.
--
Kalle Valo
_______________________________________________
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: Govind Singh <govinds@codeaurora.org>
Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ath10k: update HOST capability qmi message
Date: Wed, 28 Nov 2018 16:00:16 +0200 [thread overview]
Message-ID: <87lg5d715b.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20181119113101.23359-1-govinds@codeaurora.org> (Govind Singh's message of "Mon, 19 Nov 2018 17:01:01 +0530")
Govind Singh <govinds@codeaurora.org> writes:
> HOST capability interface data structures are updated
> in HL3.1 fw version. Update the qmi host capability
> members for compatibility across different firmware
> versions.
> With this change HL2.0 fw upgrade is required as this
> change breaks the backward compatibility with HL2.0 fw.
The last sentence is not making any sense to me, does it have a typo or
am I missing something?
If there's a typo I can fix it, no need to resend.
--
Kalle Valo
next prev parent reply other threads:[~2018-11-28 14:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 11:31 [PATCH] ath10k: update HOST capability qmi message Govind Singh
2018-11-19 11:31 ` Govind Singh
2018-11-28 14:00 ` Kalle Valo [this message]
2018-11-28 14:00 ` 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=87lg5d715b.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=govinds@codeaurora.org \
--cc=linux-wireless@vger.kernel.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.