From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: linux@roeck-us.net, gregkh@linuxfoundation.org,
bjorn.andersson@linaro.org, robh+dt@kernel.org,
linux-usb@vger.kernel.org, linux-arm-msm@vger.kernel.org,
wcheng@codeaurora.org
Subject: Re: [PATCH 6/6] usb: typec: qcom: Add pm8150b TCPM driver
Date: Tue, 26 Oct 2021 08:55:43 +0100 [thread overview]
Message-ID: <189cd7d0-4e97-dfdc-c373-862b7f5b75c3@linaro.org> (raw)
In-Reply-To: <YXeyb76jh4bim3lS@kuha.fi.intel.com>
On 26/10/2021 08:46, Heikki Krogerus wrote:
> You don't have a Makefile in that new directory typec/tcpm/qcom?
> How do you compile these new drivers?
doh !
git blame drivers/usb/typec/tcpm/qcom/Makefile
fatal: no such path 'drivers/usb/typec/tcpm/qcom/Makefile' in HEAD
thanks for spotting
prev parent reply other threads:[~2021-10-26 7:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 15:09 [PATCH 0/6] Add pm8150b TPCM driver Bryan O'Donoghue
2021-10-25 15:09 ` [PATCH 1/6] dt-bindings: usb: Add qcom,pmic-usb-typec dt-binding header Bryan O'Donoghue
2021-10-25 15:09 ` [PATCH 2/6] dt-bindings: usb: Add Qualcomm PMIC type C controller YAML schema Bryan O'Donoghue
2021-10-25 15:09 ` [PATCH 3/6] dt-bindings: usb: Add qcom,pmic-usb-pdphy dt-binding header Bryan O'Donoghue
2021-10-25 15:09 ` [PATCH 4/6] dt-bindings: usb: Add Qualcomm PMIC PDPHY controller YAML schema Bryan O'Donoghue
2021-10-25 15:09 ` [PATCH 5/6] dt-bindings: usb: Add Qualcomm PMIC TCPM " Bryan O'Donoghue
2021-10-25 15:09 ` [PATCH 6/6] usb: typec: qcom: Add pm8150b TCPM driver Bryan O'Donoghue
2021-10-25 16:17 ` Guenter Roeck
2021-10-25 16:39 ` Bryan O'Donoghue
2021-10-25 20:57 ` Bryan O'Donoghue
2021-10-25 20:21 ` Randy Dunlap
2021-10-26 7:46 ` Heikki Krogerus
2021-10-26 7:55 ` Bryan O'Donoghue [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=189cd7d0-4e97-dfdc-c373-862b7f5b75c3@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh+dt@kernel.org \
--cc=wcheng@codeaurora.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