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>,
	Karolina Drobnik <karolinadrobnik@gmail.com>,
	Mike Rapoport <rppt@kernel.org>,
	Mike Rapoport <rppt@linux.ibm.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] memblock: Remove #ifdef __KERNEL__ from memblock.h
Date: Fri, 14 Jan 2022 11:25:30 +0200	[thread overview]
Message-ID: <YeFBiiDO0FUz3mpZ@kernel.org> (raw)

Hi Linus,

Please pull this small cleanup in memblock.h.

The following changes since commit df0cc57e057f18e44dac8e6c18aba47ab53202f9:

  Linux 5.16 (2022-01-09 14:55:34 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock tags/memblock-v5.17-rc1

for you to fetch changes up to a59466ee91aaa9d43889a4c51e01de087d188448:

  memblock: Remove #ifdef __KERNEL__ from memblock.h (2022-01-11 12:36:47 +0200)

----------------------------------------------------------------
memblock: Remove #ifdef __KERNEL__ from memblock.h

memblock.h is not a uAPI header, so __KERNEL__ guard can be deleted

----------------------------------------------------------------
Karolina Drobnik (1):
      memblock: Remove #ifdef __KERNEL__ from memblock.h

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

-- 
Sincerely yours,
Mike.


             reply	other threads:[~2022-01-14  9:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-14  9:25 Mike Rapoport [this message]
2022-01-16  6:45 ` [GIT PULL] memblock: Remove #ifdef __KERNEL__ from memblock.h 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=YeFBiiDO0FUz3mpZ@kernel.org \
    --to=rppt@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=karolinadrobnik@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --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.