All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 0/6] ath10k: print crc32 checksum
Date: Mon, 30 Nov 2015 17:15:40 +0200	[thread overview]
Message-ID: <87h9k3ikmb.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20151125133654.25507.10863.stgit@potku.adurom.net> (Kalle Valo's message of "Wed, 25 Nov 2015 15:37:56 +0200")

Kalle Valo <kvalo@qca.qualcomm.com> writes:

> Print crc32 checksum for firmware and board files. Also some improvements how
> we print info messages during boot.
>
> ---
>
> Kalle Valo (6):
>       ath10k: fix otp board id error message
>       ath10k: reorganise hardware and firmware info messages
>       ath10k: always show bmi chip ids and subdevice ids
>       ath10k: split driver info messages during device initialisation
>       ath10k: print crc32 checksums for firmware and board files
>       ath10k: implement fw_checksums debugfs file

All six applied.

-- 
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@qca.qualcomm.com>
To: <ath10k@lists.infradead.org>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 0/6] ath10k: print crc32 checksum
Date: Mon, 30 Nov 2015 17:15:40 +0200	[thread overview]
Message-ID: <87h9k3ikmb.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20151125133654.25507.10863.stgit@potku.adurom.net> (Kalle Valo's message of "Wed, 25 Nov 2015 15:37:56 +0200")

Kalle Valo <kvalo@qca.qualcomm.com> writes:

> Print crc32 checksum for firmware and board files. Also some improvements how
> we print info messages during boot.
>
> ---
>
> Kalle Valo (6):
>       ath10k: fix otp board id error message
>       ath10k: reorganise hardware and firmware info messages
>       ath10k: always show bmi chip ids and subdevice ids
>       ath10k: split driver info messages during device initialisation
>       ath10k: print crc32 checksums for firmware and board files
>       ath10k: implement fw_checksums debugfs file

All six applied.

-- 
Kalle Valo

  parent reply	other threads:[~2015-11-30 15:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-25 13:37 [PATCH 0/6] ath10k: print crc32 checksum Kalle Valo
2015-11-25 13:37 ` Kalle Valo
2015-11-25 13:38 ` [PATCH 1/6] ath10k: fix otp board id error message Kalle Valo
2015-11-25 13:38   ` Kalle Valo
2015-11-25 13:48   ` Sebastian Gottschall
2015-11-25 13:38 ` [PATCH 2/6] ath10k: reorganise hardware and firmware info messages Kalle Valo
2015-11-25 13:38   ` Kalle Valo
2015-11-25 13:38 ` [PATCH 3/6] ath10k: always show bmi chip ids and subdevice ids Kalle Valo
2015-11-25 13:38   ` Kalle Valo
2015-11-25 13:38 ` [PATCH 4/6] ath10k: split driver info messages during device initialisation Kalle Valo
2015-11-25 13:38   ` Kalle Valo
2015-11-25 13:38 ` [PATCH 5/6] ath10k: print crc32 checksums for firmware and board files Kalle Valo
2015-11-25 13:38   ` Kalle Valo
2015-11-25 13:38 ` [PATCH 6/6] ath10k: implement fw_checksums debugfs file Kalle Valo
2015-11-25 13:38   ` Kalle Valo
2015-11-30 15:15 ` Kalle Valo [this message]
2015-11-30 15:15   ` [PATCH 0/6] ath10k: print crc32 checksum 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=87h9k3ikmb.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.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.