All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Jackie Liu <liu.yun@linux.dev>, Mike Rapoport <rppt@kernel.org>,
	Mike Rapoport <rppt@linux.ibm.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] memblock: fix memblock_phys_alloc() section mismatch error
Date: Wed, 22 Dec 2021 19:51:50 +0200	[thread overview]
Message-ID: <YcNltr7TxsAe+fzP@kernel.org> (raw)

Hi Linus,

The following changes since commit 2585cf9dfaaddf00b069673f27bb3f8530e2039c:

  Linux 5.16-rc5 (2021-12-12 14:53:01 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock fixes-2021-12-22

for you to fetch changes up to d7f55471db2719629f773c2d6b5742a69595bfd3:

  memblock: fix memblock_phys_alloc() section mismatch error (2021-12-22 19:35:29 +0200)

----------------------------------------------------------------
memblock: fix memblock_phys_alloc() section mismatch error

There are section mismatch errors when compiler refuses to inline one-line
wrapper memblock_phys_alloc(). Make memblock_phys_alloc() __always_inline
to avoid these mismatch issues.

----------------------------------------------------------------
Jackie Liu (1):
      memblock: fix memblock_phys_alloc() section mismatch error

 include/linux/memblock.h | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

-- 
Sincerely yours,
Mike.


             reply	other threads:[~2021-12-22 17:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-22 17:51 Mike Rapoport [this message]
2021-12-22 18:23 ` [GIT PULL] memblock: fix memblock_phys_alloc() section mismatch error Linus Torvalds
2021-12-22 18:29   ` Mike Rapoport
2021-12-22 20:29 ` pr-tracker-bot

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=YcNltr7TxsAe+fzP@kernel.org \
    --to=rppt@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=liu.yun@linux.dev \
    --cc=rppt@linux.ibm.com \
    --cc=torvalds@linux-foundation.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 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.