From: Tejun Heo <tj@kernel.org>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: linux-ide@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
Matthias Brugger <mbrugger@suse.com>
Subject: Re: [PATCH 2/2] ahci: mtk: Change driver name to ahci-mtk
Date: Mon, 4 Dec 2017 12:35:52 -0800 [thread overview]
Message-ID: <20171204203552.GI2421075@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <20171201104722.17353-1-matthias.bgg@gmail.com>
On Fri, Dec 01, 2017 at 11:47:22AM +0100, Matthias Brugger wrote:
> The driver name "ahci" is already used by the ahci platform driver.
> This leads to the following error:
> Error: Driver 'ahci' is already registered, aborting...
>
> Change the name to ahci-mtk to fix this.
>
> Signed-off-by: Matthias Brugger <mbrugger@suse.com>
Applied to libata/for-4.15-fixes.
Thanks.
--
tejun
WARNING: multiple messages have this Message-ID (diff)
From: tj@kernel.org (Tejun Heo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ahci: mtk: Change driver name to ahci-mtk
Date: Mon, 4 Dec 2017 12:35:52 -0800 [thread overview]
Message-ID: <20171204203552.GI2421075@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <20171201104722.17353-1-matthias.bgg@gmail.com>
On Fri, Dec 01, 2017 at 11:47:22AM +0100, Matthias Brugger wrote:
> The driver name "ahci" is already used by the ahci platform driver.
> This leads to the following error:
> Error: Driver 'ahci' is already registered, aborting...
>
> Change the name to ahci-mtk to fix this.
>
> Signed-off-by: Matthias Brugger <mbrugger@suse.com>
Applied to libata/for-4.15-fixes.
Thanks.
--
tejun
next prev parent reply other threads:[~2017-12-04 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 10:47 [PATCH 2/2] ahci: mtk: Change driver name to ahci-mtk Matthias Brugger
2017-12-01 10:47 ` Matthias Brugger
2017-12-04 20:35 ` Tejun Heo [this message]
2017-12-04 20:35 ` Tejun Heo
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=20171204203552.GI2421075@devbig577.frc2.facebook.com \
--to=tj@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mbrugger@suse.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 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.