All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li Yang <leoyang.li@nxp.com>
To: arm@kernel.org, soc@kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, shawnguo@kernel.org
Subject: [GIT PULL] soc/fsl driver fix for 5.10
Date: Wed, 25 Nov 2020 10:59:22 -0600	[thread overview]
Message-ID: <20201125165922.15487-1-leoyang.li@nxp.com> (raw)

Hi arm-soc maintainers,

Please find the pull request for NXP/FSL SoC drivers.

Regards,
Leo

The following changes since commit 3650b228f83adda7e5ee532e2b90429c03f7b9ec:

  Linux 5.10-rc1 (2020-10-25 15:14:11 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/leo/linux.git tags/soc-fsl-fix-v5.10

for you to fetch changes up to 2663b3388551230cbc4606a40fabf3331ceb59e4:

  soc: fsl: dpio: Get the cpumask through cpumask_of(cpu) (2020-11-23 19:27:45 -0600)

----------------------------------------------------------------
NXP/FSL SoC driver fix for 5.10

DPAA2 DPIO driver
- Fix non-static cpumask for irq affinity setting

----------------------------------------------------------------
Hao Si (1):
      soc: fsl: dpio: Get the cpumask through cpumask_of(cpu)

 drivers/soc/fsl/dpio/dpio-driver.c | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

WARNING: multiple messages have this Message-ID (diff)
From: Li Yang <leoyang.li@nxp.com>
To: arm@kernel.org, soc@kernel.org
Cc: shawnguo@kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] soc/fsl driver fix for 5.10
Date: Wed, 25 Nov 2020 10:59:22 -0600	[thread overview]
Message-ID: <20201125165922.15487-1-leoyang.li@nxp.com> (raw)
Message-ID: <20201125165922.lT9cUT54NEf1UaQdHjWIq2Tu8Pl4HZaSkPXsu6nok4c@z> (raw)

Hi arm-soc maintainers,

Please find the pull request for NXP/FSL SoC drivers.

Regards,
Leo

The following changes since commit 3650b228f83adda7e5ee532e2b90429c03f7b9ec:

  Linux 5.10-rc1 (2020-10-25 15:14:11 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/leo/linux.git tags/soc-fsl-fix-v5.10

for you to fetch changes up to 2663b3388551230cbc4606a40fabf3331ceb59e4:

  soc: fsl: dpio: Get the cpumask through cpumask_of(cpu) (2020-11-23 19:27:45 -0600)

----------------------------------------------------------------
NXP/FSL SoC driver fix for 5.10

DPAA2 DPIO driver
- Fix non-static cpumask for irq affinity setting

----------------------------------------------------------------
Hao Si (1):
      soc: fsl: dpio: Get the cpumask through cpumask_of(cpu)

 drivers/soc/fsl/dpio/dpio-driver.c | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2020-11-25 16:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-25 16:59 Li Yang [this message]
2020-11-25 16:59 ` [GIT PULL] soc/fsl driver fix for 5.10 Li Yang
2020-11-26 21:17 ` Arnd Bergmann
2020-11-26 21:17   ` Arnd Bergmann
2020-11-26 21:20 ` patchwork-bot+linux-soc

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=20201125165922.15487-1-leoyang.li@nxp.com \
    --to=leoyang.li@nxp.com \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shawnguo@kernel.org \
    --cc=soc@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 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.