From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Michael Straube <straube.linux@gmail.com>
Cc: Martin Kaiser <martin@kaiser.cx>,
Larry Finger <Larry.Finger@lwfinger.net>,
Phillip Potter <phil@philpotter.co.uk>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] staging: r8188eu: Makefile: don't overwrite global settings
Date: Mon, 18 Oct 2021 16:46:13 +0200 [thread overview]
Message-ID: <YW2ItagPdQTgWlg4@kroah.com> (raw)
In-Reply-To: <c66442a2-51fd-70bf-d9cf-5991c0d88a76@gmail.com>
On Sun, Oct 17, 2021 at 02:18:30PM +0200, Michael Straube wrote:
> On 10/16/21 19:35, Martin Kaiser wrote:
> > Remove settings from the Makefile that are set by higher-level Makefiles.
> >
> > Some of those settings might have been useful when the driver was
> > maintained out of tree.
> >
> > Signed-off-by: Martin Kaiser <martin@kaiser.cx>
> > ---
> > drivers/staging/r8188eu/Makefile | 14 --------------
> > 1 file changed, 14 deletions(-)
> >
> > diff --git a/drivers/staging/r8188eu/Makefile b/drivers/staging/r8188eu/Makefile
> > index fccf7e6d1520..8294fb69ecf9 100644
> > --- a/drivers/staging/r8188eu/Makefile
> > +++ b/drivers/staging/r8188eu/Makefile
> > @@ -1,8 +1,3 @@
> > -SHELL := /bin/bash
> > -EXTRA_CFLAGS += $(USER_EXTRA_CFLAGS)
> > -EXTRA_CFLAGS += -O1
> > -
> > -ccflags-y += -D__CHECK_ENDIAN__
> > OUTSRC_FILES := \
> > hal/HalHWImg8188E_MAC.o \
> > @@ -46,15 +41,6 @@ _OS_INTFS_FILES := \
> > _HAL_INTFS_FILES += $(OUTSRC_FILES)
> > -SUBARCH := $(shell uname -m | sed -e "s/i.86/i386/; s/ppc.*/powerpc/; s/armv.l/arm/; s/aarch64/arm64/;")
> > -
> > -ARCH ?= $(SUBARCH)
> > -CROSS_COMPILE ?=
> > -KVER ?= $(if $(KERNELRELEASE),$(KERNELRELEASE),$(shell uname -r))
> > -KSRC ?= $(if $(KERNEL_SRC),$(KERNEL_SRC),/lib/modules/$(KVER)/build)
> > -MODDESTDIR := /lib/modules/$(KVER)/kernel/drivers/net/wireless
> > -INSTALL_PREFIX :=
> > -
> > rtk_core := \
> > core/rtw_ap.o \
> > core/rtw_br_ext.o \
> >
>
> Hi Martin, this patch introduces a GCC warning on my system.
>
> drivers/staging/r8188eu/os_dep/ioctl_linux.c: In function
> 'rtw_wx_set_enc_ext':
> drivers/staging/r8188eu/os_dep/ioctl_linux.c:1929:9: warning: 'strncpy'
> specified bound 16 equals destination size [-Wstringop-truncation]
> 1929 | strncpy((char *)param->u.crypt.alg, alg_name,
> IEEE_CRYPT_ALG_NAME_LEN);
> |
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
As you all found out, that's due to the -O1 removal which was hiding
this mess :(
let me see if I can fix this up...
greg k-h
next prev parent reply other threads:[~2021-10-18 14:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-16 17:35 [PATCH 0/3] staging: r8188eu: clean up the Makefile Martin Kaiser
2021-10-16 17:35 ` [PATCH 1/3] staging: r8188eu: Makefile: remove unused driver config Martin Kaiser
2021-10-17 12:15 ` Michael Straube
2021-10-16 17:35 ` [PATCH 2/3] staging: r8188eu: Makefile: don't overwrite global settings Martin Kaiser
2021-10-17 12:18 ` Michael Straube
2021-10-17 17:46 ` Martin Kaiser
2021-10-17 20:46 ` Michael Straube
2021-10-18 14:52 ` Greg Kroah-Hartman
2021-10-18 22:33 ` Michael Straube
2021-10-18 14:46 ` Greg Kroah-Hartman [this message]
2021-10-16 17:35 ` [PATCH 3/3] staging: r8188eu: Makefile: use one file list Martin Kaiser
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=YW2ItagPdQTgWlg4@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=martin@kaiser.cx \
--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