From: Xu Yilun <yilun.xu@intel.com>
To: broonie@kernel.org, linux-spi@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: trix@redhat.com, hao.wu@intel.com,
matthew.gerlach@linux.intel.com, russell.h.weight@intel.com,
yilun.xu@intel.com
Subject: [PATCH 0/2] Some fixes for spi-altera
Date: Wed, 24 Jun 2020 09:31:24 +0800 [thread overview]
Message-ID: <1592962286-25752-1-git-send-email-yilun.xu@intel.com> (raw)
Two fixes for indirect access support patchset.
Xu Yilun (2):
spi: altera: fix driver matching failure of the device ID "spi_altera"
spi: altera: fix module autoload
drivers/spi/spi-altera.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
--
2.7.4
next reply other threads:[~2020-06-24 1:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 1:31 Xu Yilun [this message]
2020-06-24 1:31 ` [PATCH 1/2] spi: altera: fix driver matching failure of the device ID "spi_altera" Xu Yilun
2020-06-24 1:31 ` [PATCH 2/2] spi: altera: fix module autoload Xu Yilun
2020-06-24 15:38 ` [PATCH 0/2] Some fixes for spi-altera 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=1592962286-25752-1-git-send-email-yilun.xu@intel.com \
--to=yilun.xu@intel.com \
--cc=broonie@kernel.org \
--cc=hao.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=matthew.gerlach@linux.intel.com \
--cc=russell.h.weight@intel.com \
--cc=trix@redhat.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;
as well as URLs for NNTP newsgroup(s).