From: Sean Wang <sean.wang@mediatek.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: <ulf.hansson@linaro.org>, Johan Hedberg <johan.hedberg@gmail.com>,
<linux-mmc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-bluetooth@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH v1 1/2] mmc: add SDIO identifiers for MediaTek Bluetooth devices
Date: Tue, 12 Mar 2019 05:41:52 +0800 [thread overview]
Message-ID: <1552340512.17993.4.camel@mtkswgap22> (raw)
In-Reply-To: <7C99941A-306E-4233-9EA4-5D681308C490@holtmann.org>
On Mon, 2019-03-11 at 17:38 +0100, Marcel Holtmann wrote:
> Hi Sean,
>
> > The SDIO identifier for MediaTek Bluetooth devices were defined in the
> > MediaTek Bluetooth driver. Moving the definitions in MMC header file
> > seems common sense.
> >
> > Signed-off-by: Sean Wang <sean.wang@mediatek.com>
> > ---
> > include/linux/mmc/sdio_ids.h | 2 ++
> > 1 file changed, 2 insertions(+)
>
> patch has been applied to bluetooth-next tree.
>
> Can we also update the sdio.ids database inside systemd.
>
> https://github.com/systemd/systemd/blob/master/hwdb/sdio.ids
>
Sure, thanks for showing me the information and I'll update the database
for the card.
> Regards
>
> Marcel
>
>
> _______________________________________________
> Linux-mediatek mailing list
> Linux-mediatek@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-mediatek
next prev parent reply other threads:[~2019-03-11 21:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 1:15 [PATCH v1 0/2] Bluetooth: mediatek: add support for MediaTek MT7663S and MT7668S SDIO devices sean.wang
2019-03-08 1:15 ` [PATCH v1 1/2] mmc: add SDIO identifiers for MediaTek Bluetooth devices sean.wang
2019-03-11 16:38 ` Marcel Holtmann
2019-03-11 21:41 ` Sean Wang [this message]
2019-03-08 1:15 ` [PATCH v1 2/2] Bluetooth: mediatek: add support for MediaTek MT7663S and MT7668S SDIO devices sean.wang
2019-03-11 16:38 ` Marcel Holtmann
2019-03-11 21:39 ` Sean Wang
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=1552340512.17993.4.camel@mtkswgap22 \
--to=sean.wang@mediatek.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=ulf.hansson@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 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).