From: Martin Kaiser <martin@kaiser.cx>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Phillip Potter <phil@philpotter.co.uk>,
Michael Straube <straube.linux@gmail.com>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Martin Kaiser <martin@kaiser.cx>
Subject: [PATCH 0/3] staging: r8188eu: clean up PatchID / customer id
Date: Wed, 6 Oct 2021 11:09:46 +0200 [thread overview]
Message-ID: <20211006090949.1694-1-martin@kaiser.cx> (raw)
This series should be applied on top of the series I sent yesterday
(starting with Message-Id: <20211005200821.19783-1-martin@kaiser.cx>)
Thanks,
Martin
Martin Kaiser (3):
staging: r8188eu: hal data's customer id is always 0
staging: r8188eu: Odm PatchID is always 0
staging: r8188eu: merge two signal scale mapping functions
drivers/staging/r8188eu/hal/odm.c | 7 --
drivers/staging/r8188eu/hal/odm_HWConfig.c | 65 +++++--------------
drivers/staging/r8188eu/hal/rtl8188e_dm.c | 1 -
drivers/staging/r8188eu/hal/usb_halinit.c | 2 +-
drivers/staging/r8188eu/include/odm.h | 2 -
.../staging/r8188eu/include/rtl8188e_hal.h | 2 -
drivers/staging/r8188eu/include/rtw_eeprom.h | 55 ----------------
7 files changed, 19 insertions(+), 115 deletions(-)
--
2.20.1
next reply other threads:[~2021-10-06 9:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 9:09 Martin Kaiser [this message]
2021-10-06 9:09 ` [PATCH 1/3] staging: r8188eu: hal data's customer id is always 0 Martin Kaiser
2021-10-06 9:09 ` [PATCH 2/3] staging: r8188eu: Odm PatchID " Martin Kaiser
2021-10-06 9:09 ` [PATCH 3/3] staging: r8188eu: merge two signal scale mapping functions Martin Kaiser
2021-10-06 18:39 ` [PATCH 0/3] staging: r8188eu: clean up PatchID / customer id Michael Straube
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=20211006090949.1694-1-martin@kaiser.cx \
--to=martin@kaiser.cx \
--cc=Larry.Finger@lwfinger.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=phil@philpotter.co.uk \
--cc=straube.linux@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®