All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julia Lawall <Julia.Lawall@inria.fr>
To: linux-scsi@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org,
	MPT-FusionLinux.pdl@broadcom.com, linux-crypto@vger.kernel.org,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, alsa-devel@alsa-project.org,
	Sergey Shtylyov <s.shtylyov@omp.ru>,
	linux-ide@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: [PATCH 0/9] use GFP_KERNEL
Date: Thu, 10 Feb 2022 21:42:14 +0100	[thread overview]
Message-ID: <20220210204223.104181-1-Julia.Lawall@inria.fr> (raw)

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.

---

 drivers/ata/pata_mpc52xx.c               |    2 +-
 drivers/crypto/ux500/cryp/cryp_core.c    |    2 +-
 drivers/crypto/ux500/hash/hash_core.c    |    2 +-
 drivers/media/pci/cx18/cx18-driver.c     |    2 +-
 drivers/media/platform/fsl-viu.c         |    2 +-
 drivers/message/fusion/mptspi.c          |    2 +-
 drivers/mfd/sta2x11-mfd.c                |    2 +-
 drivers/mtd/devices/spear_smi.c          |    2 +-
 drivers/net/ethernet/moxa/moxart_ether.c |    4 ++--
 sound/soc/intel/boards/bytcr_wm5102.c    |    2 +-
 10 files changed, 11 insertions(+), 11 deletions(-)

WARNING: multiple messages have this Message-ID
From: Julia Lawall <Julia.Lawall@inria.fr>
To: 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: [PATCH 0/9] use GFP_KERNEL
Date: Thu, 10 Feb 2022 21:42:14 +0100	[thread overview]
Message-ID: <20220210204223.104181-1-Julia.Lawall@inria.fr> (raw)

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.

---

 drivers/ata/pata_mpc52xx.c               |    2 +-
 drivers/crypto/ux500/cryp/cryp_core.c    |    2 +-
 drivers/crypto/ux500/hash/hash_core.c    |    2 +-
 drivers/media/pci/cx18/cx18-driver.c     |    2 +-
 drivers/media/platform/fsl-viu.c         |    2 +-
 drivers/message/fusion/mptspi.c          |    2 +-
 drivers/mfd/sta2x11-mfd.c                |    2 +-
 drivers/mtd/devices/spear_smi.c          |    2 +-
 drivers/net/ethernet/moxa/moxart_ether.c |    4 ++--
 sound/soc/intel/boards/bytcr_wm5102.c    |    2 +-
 10 files changed, 11 insertions(+), 11 deletions(-)

WARNING: multiple messages have this Message-ID
From: Julia Lawall <Julia.Lawall@inria.fr>
To: linux-scsi@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org,
	MPT-FusionLinux.pdl@broadcom.com, linux-crypto@vger.kernel.org,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, alsa-devel@alsa-project.org,
	Sergey Shtylyov <s.shtylyov@omp.ru>,
	linux-ide@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: [PATCH 0/9] use GFP_KERNEL
Date: Thu, 10 Feb 2022 21:42:14 +0100	[thread overview]
Message-ID: <20220210204223.104181-1-Julia.Lawall@inria.fr> (raw)

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.

---

 drivers/ata/pata_mpc52xx.c               |    2 +-
 drivers/crypto/ux500/cryp/cryp_core.c    |    2 +-
 drivers/crypto/ux500/hash/hash_core.c    |    2 +-
 drivers/media/pci/cx18/cx18-driver.c     |    2 +-
 drivers/media/platform/fsl-viu.c         |    2 +-
 drivers/message/fusion/mptspi.c          |    2 +-
 drivers/mfd/sta2x11-mfd.c                |    2 +-
 drivers/mtd/devices/spear_smi.c          |    2 +-
 drivers/net/ethernet/moxa/moxart_ether.c |    4 ++--
 sound/soc/intel/boards/bytcr_wm5102.c    |    2 +-
 10 files changed, 11 insertions(+), 11 deletions(-)

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

             reply	other threads:[~2022-02-10 20:43 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 20:42 Julia Lawall [this message]
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 ` [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 ` (subset) " Mark Brown
2022-02-14 12:54   ` 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=20220210204223.104181-1-Julia.Lawall@inria.fr \
    --to=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.