From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Stanley Chu <stanley.chu@mediatek.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, andy.teng@mediatek.com,
jejb@linux.ibm.com, chun-hung.wu@mediatek.com,
kuohong.wang@mediatek.com, linux-kernel@vger.kernel.org,
avri.altman@wdc.com, linux-mediatek@lists.infradead.org,
peter.wang@mediatek.com, alim.akhtar@samsung.com,
matthias.bgg@gmail.com, pedrom.sousa@synopsys.com,
linux-arm-kernel@lists.infradead.org, beanhuo@micron.com
Subject: Re: [PATCH v1 0/4] scsi: ufs-mediatek: provide power management
Date: Thu, 19 Dec 2019 21:25:27 -0500 [thread overview]
Message-ID: <yq15zibag2w.fsf@oracle.com> (raw)
In-Reply-To: <1576805118.13056.31.camel@mtkswgap22> (Stanley Chu's message of "Fri, 20 Dec 2019 09:25:18 +0800")
Stanley,
> Otherwise missing header "include/linux/soc/mediatek/mtk_sip_svc.h"
> will cause build error if MediaTek UFS driver is enabled.
Thanks for the heads-up. I obviously don't have an easy way to verify. I
did check after applying to see if there was a way I could trigger a
build of the driver on a non MediaTek platform. But that didn't appear
to be trivial.
--
Martin K. Petersen Oracle Linux Engineering
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Stanley Chu <stanley.chu@mediatek.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
<linux-scsi@vger.kernel.org>, <andy.teng@mediatek.com>,
<jejb@linux.ibm.com>, <chun-hung.wu@mediatek.com>,
<kuohong.wang@mediatek.com>, <linux-kernel@vger.kernel.org>,
<avri.altman@wdc.com>, <linux-mediatek@lists.infradead.org>,
<peter.wang@mediatek.com>, <alim.akhtar@samsung.com>,
<matthias.bgg@gmail.com>, <pedrom.sousa@synopsys.com>,
<linux-arm-kernel@lists.infradead.org>, <beanhuo@micron.com>
Subject: Re: [PATCH v1 0/4] scsi: ufs-mediatek: provide power management
Date: Thu, 19 Dec 2019 21:25:27 -0500 [thread overview]
Message-ID: <yq15zibag2w.fsf@oracle.com> (raw)
In-Reply-To: <1576805118.13056.31.camel@mtkswgap22> (Stanley Chu's message of "Fri, 20 Dec 2019 09:25:18 +0800")
Stanley,
> Otherwise missing header "include/linux/soc/mediatek/mtk_sip_svc.h"
> will cause build error if MediaTek UFS driver is enabled.
Thanks for the heads-up. I obviously don't have an easy way to verify. I
did check after applying to see if there was a way I could trigger a
build of the driver on a non MediaTek platform. But that didn't appear
to be trivial.
--
Martin K. Petersen Oracle Linux Engineering
WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Stanley Chu <stanley.chu@mediatek.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, andy.teng@mediatek.com,
jejb@linux.ibm.com, chun-hung.wu@mediatek.com,
kuohong.wang@mediatek.com, linux-kernel@vger.kernel.org,
avri.altman@wdc.com, linux-mediatek@lists.infradead.org,
peter.wang@mediatek.com, alim.akhtar@samsung.com,
matthias.bgg@gmail.com, pedrom.sousa@synopsys.com,
linux-arm-kernel@lists.infradead.org, beanhuo@micron.com
Subject: Re: [PATCH v1 0/4] scsi: ufs-mediatek: provide power management
Date: Thu, 19 Dec 2019 21:25:27 -0500 [thread overview]
Message-ID: <yq15zibag2w.fsf@oracle.com> (raw)
In-Reply-To: <1576805118.13056.31.camel@mtkswgap22> (Stanley Chu's message of "Fri, 20 Dec 2019 09:25:18 +0800")
Stanley,
> Otherwise missing header "include/linux/soc/mediatek/mtk_sip_svc.h"
> will cause build error if MediaTek UFS driver is enabled.
Thanks for the heads-up. I obviously don't have an easy way to verify. I
did check after applying to see if there was a way I could trigger a
build of the driver on a non MediaTek platform. But that didn't appear
to be trivial.
--
Martin K. Petersen Oracle Linux Engineering
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-12-20 2:26 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 8:11 [PATCH v1 0/4] scsi: ufs-mediatek: provide power management Stanley Chu
2019-12-13 8:11 ` Stanley Chu
2019-12-13 8:11 ` Stanley Chu
2019-12-13 8:11 ` [PATCH v1 1/4] scsi: ufs-mediatek: introduce reference clock control Stanley Chu
2019-12-13 8:11 ` Stanley Chu
2019-12-13 8:11 ` Stanley Chu
2019-12-19 18:17 ` Alim Akhtar
2019-12-19 18:17 ` Alim Akhtar
2019-12-19 18:17 ` Alim Akhtar
2019-12-13 8:11 ` [PATCH v1 2/4] scsi: ufs: export ufshcd_auto_hibern8_update for vendor usage Stanley Chu
2019-12-13 8:11 ` Stanley Chu
2019-12-13 8:11 ` Stanley Chu
2019-12-18 23:53 ` Asutosh Das (asd)
2019-12-18 23:53 ` Asutosh Das (asd)
2019-12-18 23:53 ` Asutosh Das (asd)
2019-12-19 18:32 ` Alim Akhtar
2019-12-19 18:32 ` Alim Akhtar
2019-12-19 18:32 ` Alim Akhtar
2019-12-13 8:11 ` [PATCH v1 3/4] scsi: ufs-mediatek: configure customized auto-hibern8 timer Stanley Chu
2019-12-13 8:11 ` Stanley Chu
2019-12-13 8:11 ` Stanley Chu
2019-12-19 18:25 ` Alim Akhtar
2019-12-19 18:25 ` Alim Akhtar
2019-12-19 18:25 ` Alim Akhtar
2019-12-13 8:11 ` [PATCH v1 4/4] scsi: ufs-mediatek: configure and enable clk-gating Stanley Chu
2019-12-13 8:11 ` Stanley Chu
2019-12-13 8:11 ` Stanley Chu
2019-12-19 18:33 ` Alim Akhtar
2019-12-19 18:33 ` Alim Akhtar
2019-12-19 18:33 ` Alim Akhtar
2019-12-19 23:17 ` [PATCH v1 0/4] scsi: ufs-mediatek: provide power management Martin K. Petersen
2019-12-19 23:17 ` Martin K. Petersen
2019-12-19 23:17 ` Martin K. Petersen
2019-12-20 1:25 ` Stanley Chu
2019-12-20 1:25 ` Stanley Chu
2019-12-20 1:25 ` Stanley Chu
2019-12-20 2:25 ` Martin K. Petersen [this message]
2019-12-20 2:25 ` Martin K. Petersen
2019-12-20 2:25 ` Martin K. Petersen
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=yq15zibag2w.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=alim.akhtar@samsung.com \
--cc=andy.teng@mediatek.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=chun-hung.wu@mediatek.com \
--cc=jejb@linux.ibm.com \
--cc=kuohong.wang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=pedrom.sousa@synopsys.com \
--cc=peter.wang@mediatek.com \
--cc=stanley.chu@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 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.