From: Kalle Valo <kvalo@codeaurora.org>
To: Sebastian Gottschall <s.gottschall@dd-wrt.com>
Cc: "linux-firmware\@kernel.org" <linux-firmware@kernel.org>,
"linux-wireless\@vger.kernel.org"
<linux-wireless@vger.kernel.org>,
"ath10k\@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [PULL] ath10k firmware 20180219
Date: Tue, 27 Feb 2018 15:22:43 +0200 [thread overview]
Message-ID: <87woyysh24.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <150ef362-418d-e571-a95d-b1fa7d6db14c@dd-wrt.com> (Sebastian Gottschall's message of "Tue, 27 Feb 2018 10:05:38 +0100")
Sebastian Gottschall <s.gottschall@dd-wrt.com> writes:
> what about this?
It would be a lot easier if you could start a new thread (with a proper
subject) on ath10k@lists.infradead.org for each firmware problem you
see, instead of hijacking this thread.
And no need to CC linux-firmware maintainers either.
--
Kalle Valo
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@codeaurora.org>
To: Sebastian Gottschall <s.gottschall@dd-wrt.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
"linux-firmware@kernel.org" <linux-firmware@kernel.org>
Subject: Re: [PULL] ath10k firmware 20180219
Date: Tue, 27 Feb 2018 15:22:43 +0200 [thread overview]
Message-ID: <87woyysh24.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <150ef362-418d-e571-a95d-b1fa7d6db14c@dd-wrt.com> (Sebastian Gottschall's message of "Tue, 27 Feb 2018 10:05:38 +0100")
Sebastian Gottschall <s.gottschall@dd-wrt.com> writes:
> what about this?
It would be a lot easier if you could start a new thread (with a proper
subject) on ath10k@lists.infradead.org for each firmware problem you
see, instead of hijacking this thread.
And no need to CC linux-firmware maintainers either.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2018-02-27 13:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 10:44 [PULL] ath10k firmware 20180219 Kalle Valo
2018-02-22 10:44 ` Kalle Valo
2018-02-22 10:59 ` Sebastian Gottschall
2018-02-22 10:59 ` Sebastian Gottschall
2018-02-26 14:58 ` Kalle Valo
2018-02-26 14:58 ` Kalle Valo
2018-02-27 9:05 ` Sebastian Gottschall
2018-02-27 9:05 ` Sebastian Gottschall
2018-02-27 13:22 ` Kalle Valo [this message]
2018-02-27 13:22 ` Kalle Valo
2018-02-27 13:34 ` Sebastian Gottschall
2018-02-22 11:45 ` Josh Boyer
2018-02-22 11:45 ` Josh Boyer
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=87woyysh24.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=linux-firmware@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=s.gottschall@dd-wrt.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 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.