All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Alyssa Ross <hi@alyssa.is>
Cc: Patrice Chotard <patrice.chotard@foss.st.com>,
	Ludovic Barre <ludovic.barre@st.com>,
	Peter Griffin <peter.griffin@linaro.org>,
	"moderated list:ARM/STI ARCHITECTURE" 
	<linux-arm-kernel@lists.infradead.org>,
	"open list:DMA GENERIC OFFLOAD ENGINE SUBSYSTEM" 
	<dmaengine@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dmaengine: st_fdma: fix MODULE_ALIAS
Date: Mon, 13 Dec 2021 13:18:56 +0530	[thread overview]
Message-ID: <Ybb66JpLyJ884a5f@matsya> (raw)
In-Reply-To: <20211125154441.2626214-1-hi@alyssa.is>

On 25-11-21, 15:44, Alyssa Ross wrote:
> modprobe can't handle spaces in aliases.

Applied, thanks

-- 
~Vinod

WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vkoul@kernel.org>
To: Alyssa Ross <hi@alyssa.is>
Cc: Patrice Chotard <patrice.chotard@foss.st.com>,
	Ludovic Barre <ludovic.barre@st.com>,
	Peter Griffin <peter.griffin@linaro.org>,
	"moderated list:ARM/STI ARCHITECTURE"
	<linux-arm-kernel@lists.infradead.org>,
	 "open list:DMA GENERIC OFFLOAD ENGINE SUBSYSTEM"
	<dmaengine@vger.kernel.org>,
	 open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dmaengine: st_fdma: fix MODULE_ALIAS
Date: Mon, 13 Dec 2021 13:18:56 +0530	[thread overview]
Message-ID: <Ybb66JpLyJ884a5f@matsya> (raw)
In-Reply-To: <20211125154441.2626214-1-hi@alyssa.is>

On 25-11-21, 15:44, Alyssa Ross wrote:
> modprobe can't handle spaces in aliases.

Applied, thanks

-- 
~Vinod

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

  reply	other threads:[~2021-12-13  7:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-25 15:44 [PATCH] dmaengine: st_fdma: fix MODULE_ALIAS Alyssa Ross
2021-12-13  7:48 ` Vinod Koul [this message]
2021-12-13  7:48   ` Vinod Koul

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=Ybb66JpLyJ884a5f@matsya \
    --to=vkoul@kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=hi@alyssa.is \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ludovic.barre@st.com \
    --cc=patrice.chotard@foss.st.com \
    --cc=peter.griffin@linaro.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.