linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	 Marek Szyprowski <m.szyprowski@samsung.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	 "Rafael J. Wysocki" <rafael@kernel.org>,
	 Cristian Ciocaltea <cristian.ciocaltea@collabora.com>,
	 "Liam R . Howlett" <Liam.Howlett@oracle.com>
Subject: Re: [PATCH] regcache: use map->alloc_flags also for allocating cache
Date: Wed, 28 Aug 2024 17:32:57 +0100	[thread overview]
Message-ID: <172486277725.96345.493504524354404211.b4-ty@kernel.org> (raw)
In-Reply-To: <20240828122834.3778031-1-m.szyprowski@samsung.com>

On Wed, 28 Aug 2024 14:28:34 +0200, Marek Szyprowski wrote:
> Commit fd4ebc07b4df ("regmap: Hold the regmap lock when allocating and
> freeing the cache") introduced a locking around the allocating and
> freeing a regmap cache, so adjust the memory allocation flags to the ones
> given in the regmap configuration instead of the hardcoded GFP_KERNEL.
> 
> This fixes the "BUG: sleeping function called from invalid context"
> introduced by the mentioned commit.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-next

Thanks!

[1/1] regcache: use map->alloc_flags also for allocating cache
      commit: ae0acef3822ed8908e83cd24f337891e6be64eba

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark



      reply	other threads:[~2024-08-28 16:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20240828122850eucas1p27f050ad5fb011796b89bb90be353c417@eucas1p2.samsung.com>
2024-08-28 12:28 ` Marek Szyprowski
2024-08-28 16:32   ` Mark Brown [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=172486277725.96345.493504524354404211.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=Liam.Howlett@oracle.com \
    --cc=cristian.ciocaltea@collabora.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=m.szyprowski@samsung.com \
    --cc=rafael@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