LKML Archive on
help / color / mirror / Atom feed
From: Fabio Aiuto <>
Subject: commit c7e88ecbe328 ("staging: r8188eu: remove rtw_buf_free() function")
Date: Tue, 3 Aug 2021 09:21:30 +0200	[thread overview]
Message-ID: <20210803072129.GA1422@agape.jhs> (raw)

Dear Greg,

I followed the discussion about the bug that was
introduced by commit c7e88ecbe328. But I can't
understand why this patch introduced such a bug.
In the changelog of the revert patch you wrote
that you forgot how pointers work (:-D), but
I think I forgot either (if ever known :P).

Do you have any idea of what happened? This
topic could give us all deeper understanding
of kernel memory management.

Thank you in advance,


             reply	other threads:[~2021-08-03  7:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-03  7:21 Fabio Aiuto [this message]
2021-08-03 12:23 ` Fabio M. De Francesco
2021-08-03 12:39   ` Fabio Aiuto

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210803072129.GA1422@agape.jhs \ \ \ \ \ \ \
    --subject='Re: commit c7e88ecbe328 ("staging: r8188eu: remove rtw_buf_free() function")' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).