linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Sebastian Gottschall <s.gottschall@dd-wrt.com>,
	Kalle Valo <kvalo@codeaurora.org>,
	Antonio Quartulli <a@unstable.cc>
Cc: ath9k-devel@lists.ath9k.org, linux-wireless@vger.kernel.org,
	sw@simonwunderlich.de, Antonio Quartulli <antonio@open-mesh.com>
Subject: Re: [NOT FOR MERGE] ath9k: work around key cache corruption
Date: Thu, 27 Oct 2016 17:06:42 +0200	[thread overview]
Message-ID: <1477580802.4534.20.camel@sipsolutions.net> (raw)
In-Reply-To: <62a2dc74-4a7c-d3d4-4170-4d5759b07ab3@dd-wrt.com> (sfid-20161027_165606_267532_E06CA534)

On Thu, 2016-10-27 at 09:54 +0200, Sebastian Gottschall wrote:
> all patches have a unclear license since most patches are not comming
> with any licence declaration ;-)

You should read the DCO some time. Maybe you shouldn't be sending
patches if you think so.

johannes

  reply	other threads:[~2016-10-27 15:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-18  8:35 [NOT FOR MERGE] ath9k: work around key cache corruption Antonio Quartulli
2016-10-22 13:42 ` Antonio Quartulli
2016-10-22 20:34   ` Johannes Berg
2017-01-09  8:57   ` [ath9k-devel] " Stam, Michel [FINT]
2016-10-26 14:05 ` Kalle Valo
2016-10-26 14:10   ` Antonio Quartulli
2016-10-27  6:02     ` Kalle Valo
2016-10-27  7:54       ` Sebastian Gottschall
2016-10-27 15:06         ` Johannes Berg [this message]
2016-11-14 12:50           ` [ath9k-devel] " Stam, Michel [FINT]
2016-11-14 23:25             ` Adrian Chadd
2016-11-16  8:54               ` Stam, Michel [FINT]
2016-10-26 14:43   ` Ferry Huberts

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=1477580802.4534.20.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=a@unstable.cc \
    --cc=antonio@open-mesh.com \
    --cc=ath9k-devel@lists.ath9k.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=s.gottschall@dd-wrt.com \
    --cc=sw@simonwunderlich.de \
    /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).