From: Frank Wunderlich <frank-w@public-files.de>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Frank Wunderlich" <linux@fw-web.de>,
linux-mediatek@lists.infradead.org,
"Felix Fietkau" <nbd@nbd.name>,
"Ryder Lee" <ryder.lee@mediatek.com>,
"Jianjun Wang" <jianjun.wang@mediatek.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Aw: Re: [PATCH] PCI: mediatek-gen3: change driver name to mtk-pcie-gen3
Date: Mon, 10 Oct 2022 23:06:14 +0200 [thread overview]
Message-ID: <trinity-8fc2e212-180a-4605-9c39-89bb5546c51f-1665435974865@3c-app-gmx-bap21> (raw)
In-Reply-To: <20221010205342.GA2935945@bhelgaas>
> Gesendet: Montag, 10. Oktober 2022 um 22:53 Uhr
> Von: "Bjorn Helgaas" <helgaas@kernel.org>
> Betreff: Re: [PATCH] PCI: mediatek-gen3: change driver name to mtk-pcie-gen3
>
> On Sat, Oct 08, 2022 at 06:42:11PM +0200, Frank Wunderlich wrote:
> > From: Felix Fietkau <nbd@nbd.name>
> >
> > This allows it to coexist with the other mtk pcie driver in the same
> > kernel.
> >
> > Signed-off-by: Felix Fietkau <nbd@nbd.name>
> > Signed-off-by: Frank Wunderlich <frank-w@public-files.de>
>
> Looks like Lorenzo already applied this:
>
> https://lore.kernel.org/all/166125958529.60702.17839683437013330997.b4-ty@kernel.org/#t
ok, thx for pointing out
have rebased my tree to torvalds/master from yesterday and it was not yet in...but i see it in next with commit-date from august 23th
i guess pcie-part is not yet merged...sorry for the noise
regards Frank
prev parent reply other threads:[~2022-10-10 21:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-08 16:42 [PATCH] PCI: mediatek-gen3: change driver name to mtk-pcie-gen3 Frank Wunderlich
2022-10-10 20:53 ` Bjorn Helgaas
2022-10-10 21:06 ` Frank Wunderlich [this message]
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=trinity-8fc2e212-180a-4605-9c39-89bb5546c51f-1665435974865@3c-app-gmx-bap21 \
--to=frank-w@public-files.de \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=jianjun.wang@mediatek.com \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@fw-web.de \
--cc=lpieralisi@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=nbd@nbd.name \
--cc=robh@kernel.org \
--cc=ryder.lee@mediatek.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).