linux-modules.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kernel.org Bugbot" <bugbot@kernel.org>
To: song@kernel.org, jbaron@akamai.com, bugs@lists.linux.dev,
	mcgrof@kernel.org, linux-modules@vger.kernel.org,
	jim.cromie@gmail.com, linux-kernel@vger.kernel.org,
	gregkh@linuxfoundation.org
Subject: Re: kmemleaks on ac3b43283923 ("module: replace module_layout with module_memory")
Date: Mon,  3 Apr 2023 21:20:39 +0000 (UTC)	[thread overview]
Message-ID: <20230403-b217296-67d45b5fbc27@bugzilla.kernel.org> (raw)
In-Reply-To: <CAJfuBxwomDagbdNP-Q6WvzcWsNY0Z2Lu2Yy5aZQ1d9W7Ka1_NQ@mail.gmail.com>

Hello:

This conversation is now tracked by Kernel.org Bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=217296

There is no need to do anything else, just keep talking.
-- 
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (peebz 0.1)


      parent reply	other threads:[~2023-04-03 21:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 22:45 kmemleaks on ac3b43283923 ("module: replace module_layout with module_memory") jim.cromie
2023-03-31  6:59 ` Luis Chamberlain
2023-03-31 17:08   ` jim.cromie
2023-03-31 19:12     ` Luis Chamberlain
2023-03-31 21:42       ` jim.cromie
2023-04-01  0:27   ` Song Liu
2023-04-03 20:43     ` Luis Chamberlain
2023-04-05  1:38       ` jim.cromie
2023-04-05  2:01         ` Luis Chamberlain
2023-04-06  3:14           ` jim.cromie
2023-04-06 19:53             ` Luis Chamberlain
2023-04-11 15:10       ` Catalin Marinas
2023-04-11 17:07         ` Luis Chamberlain
2023-04-11 23:00           ` Luis Chamberlain
2023-04-12  9:53             ` Catalin Marinas
2023-04-12 17:22               ` Luis Chamberlain
2023-04-03 21:10 ` Konstantin Ryabitsev
2023-04-03 21:20 ` Kernel.org Bugbot [this message]

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=20230403-b217296-67d45b5fbc27@bugzilla.kernel.org \
    --to=bugbot@kernel.org \
    --cc=bugs@lists.linux.dev \
    --cc=gregkh@linuxfoundation.org \
    --cc=jbaron@akamai.com \
    --cc=jim.cromie@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=song@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).