From: Kalle Valo <kvalo@codeaurora.org>
To: Jes Sorensen <Jes.Sorensen@redhat.com>
Cc: linux-wireless@vger.kernel.org, Larry.Finger@lwfinger.net,
Jes Sorensen <Jes.Sorensen@redhat.com>
Subject: Re: [1/4] rtl8xxxu: Fix off by one error calculating pubq
Date: Mon, 26 Sep 2016 17:42:05 +0000 (UTC) [thread overview]
Message-ID: <20160926174205.284A16159A@smtp.codeaurora.org> (raw)
In-Reply-To: <1474420769-20086-2-git-send-email-Jes.Sorensen@redhat.com>
Jes Sorensen <Jes.Sorensen@redhat.com> wrote:
> From: Jes Sorensen <Jes.Sorensen@redhat.com>
>
> This was detected tracing the 8188eu driver, but doesn't seem to make
> any difference when using it.
>
> Signed-off-by: Jes Sorensen <Jes.Sorensen@redhat.com>
4 patches applied to wireless-drivers-next.git, thanks.
3a589fae4a2c rtl8xxxu: Fix off by one error calculating pubq
c0a99bbb1b7a rtl8xxxu: Clean up llt_init() API
2fc5dd27bf9b rtl8xxxu: Use a struct rtl8xxxu_fileops * in rtl8xxxu_init_device()
b42fbed6b8a5 rtl8xxxu: Stop log spam from each successful interrupt
--
https://patchwork.kernel.org/patch/9342651/
Documentation about submitting wireless patches and checking status
from patchwork:
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2016-09-26 17:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 1:19 [PATCH 0/4] rtl8xxxu - four patches for 4.9 Jes.Sorensen
2016-09-21 1:19 ` [PATCH 1/4] rtl8xxxu: Fix off by one error calculating pubq Jes.Sorensen
2016-09-26 17:42 ` Kalle Valo [this message]
2016-09-21 1:19 ` [PATCH 2/4] rtl8xxxu: Clean up llt_init() API Jes.Sorensen
2016-09-21 1:19 ` [PATCH 3/4] rtl8xxxu: Use a struct rtl8xxxu_fileops * in rtl8xxxu_init_device() Jes.Sorensen
2016-09-21 1:19 ` [PATCH 4/4] rtl8xxxu: Stop log spam from each successful interrupt Jes.Sorensen
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=20160926174205.284A16159A@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=Jes.Sorensen@redhat.com \
--cc=Larry.Finger@lwfinger.net \
--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.