From: Kalle Valo <kvalo@kernel.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: "Stefano Brivio" <sbrivio@redhat.com>,
Jaehee <jhpark1013@gmail.com>,
"Jérôme Pouiller" <jerome.pouiller@silabs.com>,
"David S. Miller" <davem@davemloft.net>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev,
"Outreachy Linux Kernel" <outreachy@lists.linux.dev>
Subject: Re: [PATCH] wfx: use container_of() to get vif
Date: Wed, 04 May 2022 19:05:57 +0300 [thread overview]
Message-ID: <87o80d9tay.fsf@kernel.org> (raw)
In-Reply-To: <20220504132551.GD4009@kadam> (Dan Carpenter's message of "Wed, 4 May 2022 16:25:51 +0300")
Dan Carpenter <dan.carpenter@oracle.com> writes:
> On Wed, May 04, 2022 at 01:50:59PM +0200, Stefano Brivio wrote:
>> And that it's *obvious* that container_of() would trigger warnings
>> otherwise. Well, obvious just for me, it seems.
>
> :P
>
> Apparently it wasn't obvious to Kalle and me. My guess is that you saw
> the build error. Either that or Kalle and I are geezers who haven't
> looked at container_of() since before the BUILD_BUG_ON() was added five
> years ago.
Exactly, I also had to duplicate the error myself before I was able to
understand the issue. So I'm officially a geezer now :D
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-05-04 16:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 3:51 [PATCH] wfx: use container_of() to get vif Jaehee Park
2022-04-19 13:39 ` Jérôme Pouiller
2022-05-03 18:18 ` Jaehee Park
2022-04-20 11:57 ` Kalle Valo
2022-04-20 16:53 ` Fabio M. De Francesco
2022-05-02 18:10 ` Jaehee
2022-05-02 18:34 ` Jaehee Park
2022-05-04 9:33 ` Dan Carpenter
2022-05-04 11:50 ` Stefano Brivio
2022-05-04 13:25 ` Dan Carpenter
2022-05-04 16:05 ` Kalle Valo [this message]
2022-05-04 17:07 ` Jaehee Park
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=87o80d9tay.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=davem@davemloft.net \
--cc=jerome.pouiller@silabs.com \
--cc=jhpark1013@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=outreachy@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=sbrivio@redhat.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 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.