From: "Nemanov, Michael" <michael.nemanov@ti.com>
To: Simon Horman <horms@kernel.org>
Cc: Sabeeh Khan <sabeeh-khan@ti.com>, Kalle Valo <kvalo@kernel.org>,
Johannes Berg <johannes.berg@intel.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
<linux-wireless@vger.kernel.org>, <netdev@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 11/17] wifi: cc33xx: Add init.c, init.h
Date: Thu, 20 Jun 2024 19:52:21 +0300 [thread overview]
Message-ID: <8dd345ae-7da3-440f-9d9c-d2b0500ba78b@ti.com> (raw)
In-Reply-To: <20240620163048.GK959333@kernel.org>
On 6/20/2024 7:30 PM, Simon Horman wrote:
...
> Hi Michael,
>
> I tried this again with GCC 13.2.0 on x86_64 with allmodconfig.
> And I was able to see this with a W=1 (make W=1) build.
>
Oh it was the combination of CONFIG_FORTIFY_SOURCE=y (from allmodconfig)
and W=1. Thanks, I see it now.
Michael.
next prev parent reply other threads:[~2024-06-20 16:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-09 18:20 [PATCH v2 00/17] wifi: cc33xx: Add driver for new TI CC33xx wireless device family michael.nemanov
2024-06-09 18:20 ` [PATCH v2 01/17] wifi: cc33xx: Add cc33xx.h, cc33xx_i.h michael.nemanov
2024-06-09 18:20 ` [PATCH v2 02/17] wifi: cc33xx: Add debug.h michael.nemanov
2024-06-09 18:20 ` [PATCH v2 03/17] wifi: cc33xx: Add sdio.c, io.c, io.h michael.nemanov
2024-06-09 18:20 ` [PATCH v2 04/17] wifi: cc33xx: Add cmd.c, cmd.h michael.nemanov
2024-06-09 18:20 ` [PATCH v2 05/17] wifi: cc33xx: Add acx.c, acx.h michael.nemanov
2024-06-09 18:20 ` [PATCH v2 06/17] wifi: cc33xx: Add event.c, event.h michael.nemanov
2024-06-09 18:20 ` [PATCH v2 07/17] wifi: cc33xx: Add boot.c, boot.h michael.nemanov
2024-06-09 18:20 ` [PATCH v2 08/17] wifi: cc33xx: Add main.c michael.nemanov
2024-06-09 18:20 ` [PATCH v2 09/17] wifi: cc33xx: Add rx.c, rx.h michael.nemanov
2024-06-09 18:20 ` [PATCH v2 10/17] wifi: cc33xx: Add tx.c, tx.h michael.nemanov
2024-06-09 18:20 ` [PATCH v2 11/17] wifi: cc33xx: Add init.c, init.h michael.nemanov
2024-06-15 8:51 ` Simon Horman
2024-06-20 8:40 ` Nemanov, Michael
2024-06-20 16:30 ` Simon Horman
2024-06-20 16:52 ` Nemanov, Michael [this message]
2024-06-09 18:20 ` [PATCH v2 12/17] wifi: cc33xx: Add scan.c, scan.h michael.nemanov
2024-06-09 18:20 ` [PATCH v2 13/17] wifi: cc33xx: Add conf.h michael.nemanov
2024-06-09 18:20 ` [PATCH v2 14/17] wifi: cc33xx: Add ps.c, ps.h michael.nemanov
2024-06-09 18:21 ` [PATCH v2 15/17] wifi: cc33xx: Add testmode.c, testmode.h michael.nemanov
2024-06-09 18:21 ` [PATCH v2 16/17] wifi: cc33xx: Add Kconfig, Makefile Integrate cc33xx into wireless/ti folder michael.nemanov
2024-06-09 18:21 ` [PATCH v2 17/17] dt-bindings: net: wireless: cc33xx: Add ti,cc33xx.yaml michael.nemanov
2024-06-10 8:16 ` Krzysztof Kozlowski
2024-06-10 8:17 ` Krzysztof Kozlowski
2024-06-13 7:39 ` Nemanov, Michael
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=8dd345ae-7da3-440f-9d9c-d2b0500ba78b@ti.com \
--to=michael.nemanov@ti.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=johannes.berg@intel.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=sabeeh-khan@ti.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®