Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: alsa-devel@alsa-project.org
Cc: liam.r.girdwood@linux.intel.com, patches.audio@intel.com,
	broonie@kernel.org, Vinod Koul <vinod.koul@intel.com>
Subject: [PATCH 6/7] ASoC: Intel: kbl_rt5663_max98927: Replace GFP_ATOMIC with GFP_KERNEL
Date: Fri, 20 Apr 2018 16:14:31 +0530	[thread overview]
Message-ID: <1524221072-11040-7-git-send-email-vinod.koul@intel.com> (raw)
In-Reply-To: <1524221072-11040-1-git-send-email-vinod.koul@intel.com>

In kabylake_audio_probe which is not atomic context, we use GFP_ATOMIC
flag with memory allocation, fix that by using GFP_KERNEL.

Signed-off-by: Vinod Koul <vinod.koul@intel.com>
---
 sound/soc/intel/boards/kbl_rt5663_max98927.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sound/soc/intel/boards/kbl_rt5663_max98927.c b/sound/soc/intel/boards/kbl_rt5663_max98927.c
index 0e6b7e79441c..513cc65a77be 100644
--- a/sound/soc/intel/boards/kbl_rt5663_max98927.c
+++ b/sound/soc/intel/boards/kbl_rt5663_max98927.c
@@ -972,7 +972,7 @@ static int kabylake_audio_probe(struct platform_device *pdev)
 	struct skl_machine_pdata *pdata;
 	int ret;
 
-	ctx = devm_kzalloc(&pdev->dev, sizeof(*ctx), GFP_ATOMIC);
+	ctx = devm_kzalloc(&pdev->dev, sizeof(*ctx), GFP_KERNEL);
 	if (!ctx)
 		return -ENOMEM;
 
-- 
2.7.4

  parent reply	other threads:[~2018-04-20 10:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-20 10:44 [PATCH 0/7] ASoC: Intel: Replace GFP_ATOMIC with GFP_KERNEL Vinod Koul
2018-04-20 10:44 ` [PATCH 1/7] ASoC: Intel: byt-max98090: " Vinod Koul
2018-04-20 17:03   ` Applied "ASoC: Intel: byt-max98090: Replace GFP_ATOMIC with GFP_KERNEL" to the asoc tree Mark Brown
2018-04-20 10:44 ` [PATCH 2/7] ASoC: Intel: bytcht_es8316: Replace GFP_ATOMIC with GFP_KERNEL Vinod Koul
2018-04-20 17:03   ` Applied "ASoC: Intel: bytcht_es8316: Replace GFP_ATOMIC with GFP_KERNEL" to the asoc tree Mark Brown
2018-04-20 10:44 ` [PATCH 3/7] ASoC: Intel: bytcr_rt5651: Replace GFP_ATOMIC with GFP_KERNEL Vinod Koul
2018-04-20 17:02   ` Applied "ASoC: Intel: bytcr_rt5651: Replace GFP_ATOMIC with GFP_KERNEL" to the asoc tree Mark Brown
2018-04-20 10:44 ` [PATCH 4/7] ASoC: Intel: cht_bsw_nau8824: Replace GFP_ATOMIC with GFP_KERNEL Vinod Koul
2018-04-20 17:02   ` Applied "ASoC: Intel: cht_bsw_nau8824: Replace GFP_ATOMIC with GFP_KERNEL" to the asoc tree Mark Brown
2018-04-20 10:44 ` [PATCH 5/7] ASoC: Intel: kbl_da7219_max98357a: Replace GFP_ATOMIC with GFP_KERNEL Vinod Koul
2018-04-20 17:02   ` Applied "ASoC: Intel: kbl_da7219_max98357a: Replace GFP_ATOMIC with GFP_KERNEL" to the asoc tree Mark Brown
2018-04-20 10:44 ` Vinod Koul [this message]
2018-04-20 17:01   ` Applied "ASoC: Intel: kbl_rt5663_max98927: " Mark Brown
2018-04-20 10:44 ` [PATCH 7/7] ASoC: Intel: kbl_rt5663_rt5514_max98927: Replace GFP_ATOMIC with GFP_KERNEL Vinod Koul
2018-04-20 17:01   ` Applied "ASoC: Intel: kbl_rt5663_rt5514_max98927: Replace GFP_ATOMIC with GFP_KERNEL" to the asoc tree Mark Brown

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=1524221072-11040-7-git-send-email-vinod.koul@intel.com \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=patches.audio@intel.com \
    /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