All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Julia Lawall <Julia.Lawall@inria.fr>, linux-scsi@vger.kernel.org
Cc: linux-mtd@lists.infradead.org, MPT-FusionLinux.pdl@broadcom.com,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
	Sergey Shtylyov <s.shtylyov@omp.ru>,
	linux-crypto@vger.kernel.org, kernel-janitors@vger.kernel.org,
	netdev@vger.kernel.org, linux-media@vger.kernel.org,
	alsa-devel@alsa-project.org
Subject: Re: (subset) [PATCH 0/9] use GFP_KERNEL
Date: Mon, 14 Feb 2022 12:54:44 +0000	[thread overview]
Message-ID: <164484328403.12994.4553763831627919088.b4-ty@kernel.org> (raw)
In-Reply-To: <20220210204223.104181-1-Julia.Lawall@inria.fr>

On Thu, 10 Feb 2022 21:42:14 +0100, Julia Lawall wrote:
> Platform_driver and pci_driver probe functions aren't called with
> locks held and thus don't need GFP_ATOMIC. Use GFP_KERNEL instead.
> 
> All changes have been compile-tested.
> 

Applied to

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

Thanks!

[3/9] ASoC: Intel: bytcr_wm5102: use GFP_KERNEL
      commit: 695c105933cfa04ccf84088342193ae43e37e0f5

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

WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Julia Lawall <Julia.Lawall@inria.fr>, linux-scsi@vger.kernel.org
Cc: alsa-devel@alsa-project.org, Sergey Shtylyov <s.shtylyov@omp.ru>,
	netdev@vger.kernel.org, kernel-janitors@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
	linux-mtd@lists.infradead.org, linux-crypto@vger.kernel.org,
	MPT-FusionLinux.pdl@broadcom.com, linux-media@vger.kernel.org
Subject: Re: (subset) [PATCH 0/9] use GFP_KERNEL
Date: Mon, 14 Feb 2022 12:54:44 +0000	[thread overview]
Message-ID: <164484328403.12994.4553763831627919088.b4-ty@kernel.org> (raw)
In-Reply-To: <20220210204223.104181-1-Julia.Lawall@inria.fr>

On Thu, 10 Feb 2022 21:42:14 +0100, Julia Lawall wrote:
> Platform_driver and pci_driver probe functions aren't called with
> locks held and thus don't need GFP_ATOMIC. Use GFP_KERNEL instead.
> 
> All changes have been compile-tested.
> 

Applied to

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

Thanks!

[3/9] ASoC: Intel: bytcr_wm5102: use GFP_KERNEL
      commit: 695c105933cfa04ccf84088342193ae43e37e0f5

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

WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Julia Lawall <Julia.Lawall@inria.fr>, linux-scsi@vger.kernel.org
Cc: linux-mtd@lists.infradead.org, MPT-FusionLinux.pdl@broadcom.com,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
	Sergey Shtylyov <s.shtylyov@omp.ru>,
	linux-crypto@vger.kernel.org, kernel-janitors@vger.kernel.org,
	netdev@vger.kernel.org, linux-media@vger.kernel.org,
	alsa-devel@alsa-project.org
Subject: Re: (subset) [PATCH 0/9] use GFP_KERNEL
Date: Mon, 14 Feb 2022 12:54:44 +0000	[thread overview]
Message-ID: <164484328403.12994.4553763831627919088.b4-ty@kernel.org> (raw)
In-Reply-To: <20220210204223.104181-1-Julia.Lawall@inria.fr>

On Thu, 10 Feb 2022 21:42:14 +0100, Julia Lawall wrote:
> Platform_driver and pci_driver probe functions aren't called with
> locks held and thus don't need GFP_ATOMIC. Use GFP_KERNEL instead.
> 
> All changes have been compile-tested.
> 

Applied to

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

Thanks!

[3/9] ASoC: Intel: bytcr_wm5102: use GFP_KERNEL
      commit: 695c105933cfa04ccf84088342193ae43e37e0f5

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

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  parent reply	other threads:[~2022-02-14 12:54 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 20:42 [PATCH 0/9] use GFP_KERNEL Julia Lawall
2022-02-10 20:42 ` Julia Lawall
2022-02-10 20:42 ` Julia Lawall
2022-02-10 20:42 ` [PATCH 1/9] net: moxa: " Julia Lawall
2022-02-10 20:42 ` [PATCH 2/9] media: cx18: " Julia Lawall
2022-02-18 12:26   ` Dan Carpenter
2022-02-10 20:42 ` [PATCH 3/9] ASoC: Intel: bytcr_wm5102: " Julia Lawall
2022-02-10 20:42   ` Julia Lawall
2022-02-11  0:20   ` Pierre-Louis Bossart
2022-02-11  0:20     ` Pierre-Louis Bossart
2022-02-11  7:43     ` Hans de Goede
2022-02-11  7:43       ` Hans de Goede
2022-02-10 20:42 ` [PATCH 4/9] crypto: " Julia Lawall
2022-02-18  5:37   ` Herbert Xu
2022-02-10 20:42 ` [PATCH 5/9] pata_mpc52xx: " Julia Lawall
2022-02-10 20:45   ` Sergey Shtylyov
2022-02-11  7:43   ` Damien Le Moal
2022-02-10 20:42 ` [PATCH 6/9] media: fsl-viu: " Julia Lawall
2022-02-10 20:42 ` [PATCH 7/9] mtd: spear_smi: " Julia Lawall
2022-02-10 20:42   ` Julia Lawall
2022-02-18 14:32   ` Miquel Raynal
2022-02-18 14:32     ` Miquel Raynal
2022-02-10 20:42 ` [PATCH 8/9] [SCSI] mptfusion: " Julia Lawall
2022-02-11 22:10   ` Martin K. Petersen
2022-02-10 20:42 ` [PATCH 9/9] mfd: sta2x11: " Julia Lawall
2022-02-15 13:22   ` Lee Jones
2022-02-12  0:20 ` [PATCH 0/9] " patchwork-bot+netdevbpf
2022-02-12  0:20   ` patchwork-bot+netdevbpf
2022-02-14 12:54 ` Mark Brown [this message]
2022-02-14 12:54   ` (subset) " Mark Brown
2022-02-14 12:54   ` Mark Brown
2022-02-15  3:19 ` Martin K. Petersen
2022-02-15  3:19   ` Martin K. Petersen
2022-02-15  3:19   ` Martin K. Petersen

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=164484328403.12994.4553763831627919088.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=Julia.Lawall@inria.fr \
    --cc=MPT-FusionLinux.pdl@broadcom.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=s.shtylyov@omp.ru \
    /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.