From: Suren Baghdasaryan <surenb@google.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: akpm@linux-foundation.org, kent.overstreet@linux.dev,
vbabka@suse.cz, pasha.tatashin@soleen.com,
souravpanda@google.com, keescook@chromium.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH 1/1] alloc_tag: Export memory allocation profiling symbols used by modules
Date: Tue, 16 Jul 2024 18:22:10 -0700 [thread overview]
Message-ID: <CAJuCfpFmfMH0=qOUz=Z_-QjgguhL4XKbZZ2ahx26HyYC23NGWg@mail.gmail.com> (raw)
In-Reply-To: <CAJuCfpHX9SzPBTxQg2NjKPjbeD60HAotdK6DqnFmn3crvnGdvQ@mail.gmail.com>
On Fri, Jul 12, 2024 at 6:27 AM Suren Baghdasaryan <surenb@google.com> wrote:
>
> On Thu, Jul 11, 2024 at 9:25 PM Christoph Hellwig <hch@infradead.org> wrote:
> >
> > On Thu, Jul 11, 2024 at 01:46:26PM -0700, Suren Baghdasaryan wrote:
> > > +EXPORT_SYMBOL(page_ext_get);
> >
> > > +EXPORT_SYMBOL(page_ext_put);
> >
> > These really have no business being exported, especially non-GPL.
> > Please rework whatever interfaces need them to be be moved out of line.
>
> Ok, I can do that. Thanks for the feedback!
Replacement patches are posted at
https://lore.kernel.org/all/20240717011631.2150066-1-surenb@google.com
Andrew, could you please replace this older patch with the new
patchset (2 patches now)? I can see the old patch in mm-unstable as
ac5ca7954e4e ("alloc_tag: export memory allocation profiling symbols
used by modules") and I think it's also in your mm-hotfixes-stable.
Please replace it with new patches.
Thanks,
Suren.
>
> >
prev parent reply other threads:[~2024-07-17 1:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 20:46 Suren Baghdasaryan
2024-07-11 21:07 ` Andrew Morton
2024-07-11 21:38 ` Suren Baghdasaryan
2024-07-12 4:25 ` Christoph Hellwig
2024-07-12 13:27 ` Suren Baghdasaryan
2024-07-17 1:22 ` Suren Baghdasaryan [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='CAJuCfpFmfMH0=qOUz=Z_-QjgguhL4XKbZZ2ahx26HyYC23NGWg@mail.gmail.com' \
--to=surenb@google.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=keescook@chromium.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=pasha.tatashin@soleen.com \
--cc=souravpanda@google.com \
--cc=vbabka@suse.cz \
/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