From: Greg KH <gregkh@linuxfoundation.org>
To: Georgi Djakov <georgi.djakov@linaro.org>
Cc: sanjayc@nvidia.com, maxime.ripard@bootlin.com,
mturquette@baylibre.com, daidavid1@codeaurora.org,
bjorn.andersson@linaro.org, skannan@codeaurora.org,
abailon@baylibre.com, vincent.guittot@linaro.org,
seansw@qti.qualcomm.com, khilman@baylibre.com,
evgreen@chromium.org, ksitaraman@nvidia.com,
devicetree@vger.kernel.org, arnd@arndb.de,
linux-pm@vger.kernel.org, linux-arm-msm@vger.kernel.org,
henryc.chen@mediatek.com, andy.gross@linaro.org,
robh+dt@kernel.org, linux-mediatek@lists.infradead.org,
linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, rjw@rjwysocki.net,
dianders@chromium.org, amit.kucheria@linaro.org,
linux-kernel@vger.kernel.org, thierry.reding@gmail.com,
olof@lixom.net
Subject: Re: [PATCH v13 0/8] Introduce on-chip interconnect API
Date: Tue, 22 Jan 2019 16:00:49 +0100 [thread overview]
Message-ID: <20190122150048.GA11466@kroah.com> (raw)
In-Reply-To: <2ac9b994-ecbf-05fd-5c01-7ecd0089c744@linaro.org>
On Tue, Jan 22, 2019 at 04:45:20PM +0200, Georgi Djakov wrote:
> On 1/22/19 14:42, Greg KH wrote:
> > On Wed, Jan 16, 2019 at 06:10:55PM +0200, Georgi Djakov wrote:
> [..]
> >
> > All now queued up, thanks.
> >
> > greg k-h
>
> Hi Greg,
>
> Thanks for considering these patches! Actually i have a branch named
> icc-next [1] which is pulled into linux-next. I will drop these same
> patches to avoid conflicts.
>
> If all is well, i was wondering how to proceed with follow-up patches.
> Some consumers of this API are already floating on the lists. How about
> sending you a pull request before the merge window with the collected
> patches?
Sure, that works, or you can just send them as patches, either works for
me.
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Georgi Djakov <georgi.djakov@linaro.org>
Cc: sanjayc@nvidia.com, maxime.ripard@bootlin.com,
mturquette@baylibre.com, daidavid1@codeaurora.org,
bjorn.andersson@linaro.org, skannan@codeaurora.org,
abailon@baylibre.com, vincent.guittot@linaro.org,
seansw@qti.qualcomm.com, khilman@baylibre.com,
evgreen@chromium.org, ksitaraman@nvidia.com,
devicetree@vger.kernel.org, arnd@arndb.de,
linux-pm@vger.kernel.org, linux-arm-msm@vger.kernel.org,
henryc.chen@mediatek.com, andy.gross@linaro.org,
robh+dt@kernel.org, linux-mediatek@lists.infradead.org,
linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, rjw@rjwysocki.net,
dianders@chromium.org, amit.kucheria@linaro.org,
linux-kernel@vger.kernel.org, thierry.reding@gmail.com,
olof@lixom.net
Subject: Re: [PATCH v13 0/8] Introduce on-chip interconnect API
Date: Tue, 22 Jan 2019 16:00:49 +0100 [thread overview]
Message-ID: <20190122150048.GA11466@kroah.com> (raw)
In-Reply-To: <2ac9b994-ecbf-05fd-5c01-7ecd0089c744@linaro.org>
On Tue, Jan 22, 2019 at 04:45:20PM +0200, Georgi Djakov wrote:
> On 1/22/19 14:42, Greg KH wrote:
> > On Wed, Jan 16, 2019 at 06:10:55PM +0200, Georgi Djakov wrote:
> [..]
> >
> > All now queued up, thanks.
> >
> > greg k-h
>
> Hi Greg,
>
> Thanks for considering these patches! Actually i have a branch named
> icc-next [1] which is pulled into linux-next. I will drop these same
> patches to avoid conflicts.
>
> If all is well, i was wondering how to proceed with follow-up patches.
> Some consumers of this API are already floating on the lists. How about
> sending you a pull request before the merge window with the collected
> patches?
Sure, that works, or you can just send them as patches, either works for
me.
greg k-h
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Georgi Djakov <georgi.djakov@linaro.org>
Cc: andy.gross@linaro.org, olof@lixom.net, arnd@arndb.de,
rjw@rjwysocki.net, robh+dt@kernel.org, mturquette@baylibre.com,
khilman@baylibre.com, vincent.guittot@linaro.org,
skannan@codeaurora.org, bjorn.andersson@linaro.org,
amit.kucheria@linaro.org, seansw@qti.qualcomm.com,
daidavid1@codeaurora.org, evgreen@chromium.org,
dianders@chromium.org, abailon@baylibre.com,
maxime.ripard@bootlin.com, thierry.reding@gmail.com,
ksitaraman@nvidia.com, sanjayc@nvidia.com,
henryc.chen@mediatek.com, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v13 0/8] Introduce on-chip interconnect API
Date: Tue, 22 Jan 2019 16:00:49 +0100 [thread overview]
Message-ID: <20190122150048.GA11466@kroah.com> (raw)
In-Reply-To: <2ac9b994-ecbf-05fd-5c01-7ecd0089c744@linaro.org>
On Tue, Jan 22, 2019 at 04:45:20PM +0200, Georgi Djakov wrote:
> On 1/22/19 14:42, Greg KH wrote:
> > On Wed, Jan 16, 2019 at 06:10:55PM +0200, Georgi Djakov wrote:
> [..]
> >
> > All now queued up, thanks.
> >
> > greg k-h
>
> Hi Greg,
>
> Thanks for considering these patches! Actually i have a branch named
> icc-next [1] which is pulled into linux-next. I will drop these same
> patches to avoid conflicts.
>
> If all is well, i was wondering how to proceed with follow-up patches.
> Some consumers of this API are already floating on the lists. How about
> sending you a pull request before the merge window with the collected
> patches?
Sure, that works, or you can just send them as patches, either works for
me.
greg k-h
next prev parent reply other threads:[~2019-01-22 15:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 16:10 [PATCH v13 0/8] Introduce on-chip interconnect API Georgi Djakov
2019-01-16 16:10 ` Georgi Djakov
[not found] ` <20190116161103.6937-1-georgi.djakov-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2019-01-16 16:10 ` [PATCH v13 1/8] interconnect: Add generic " Georgi Djakov
2019-01-16 16:10 ` Georgi Djakov
2019-01-16 16:10 ` Georgi Djakov
2019-01-16 16:10 ` [PATCH v13 2/8] dt-bindings: Introduce interconnect binding Georgi Djakov
2019-01-16 16:10 ` Georgi Djakov
2019-01-16 16:10 ` [PATCH v13 3/8] interconnect: Allow endpoints translation via DT Georgi Djakov
2019-01-16 16:10 ` Georgi Djakov
2019-01-16 16:10 ` [PATCH v13 4/8] interconnect: Add debugfs support Georgi Djakov
2019-01-16 16:10 ` Georgi Djakov
2019-01-16 16:11 ` [PATCH v13 5/8] interconnect: qcom: Add sdm845 interconnect provider driver Georgi Djakov
2019-01-16 16:11 ` Georgi Djakov
2019-01-16 16:11 ` [PATCH v13 6/8] arm64: dts: sdm845: Add interconnect provider DT nodes Georgi Djakov
2019-01-16 16:11 ` Georgi Djakov
2019-01-16 16:11 ` [PATCH v13 7/8] MAINTAINERS: add a maintainer for the interconnect API Georgi Djakov
2019-01-16 16:11 ` Georgi Djakov
2019-01-16 16:11 ` [PATCH v13 8/8] interconnect: Revert to previous config if any request fails Georgi Djakov
2019-01-16 16:11 ` Georgi Djakov
2019-01-22 12:42 ` [PATCH v13 0/8] Introduce on-chip interconnect API Greg KH
2019-01-22 12:42 ` Greg KH
2019-01-22 14:45 ` Georgi Djakov
2019-01-22 14:45 ` Georgi Djakov
2019-01-22 15:00 ` Greg KH [this message]
2019-01-22 15:00 ` Greg KH
2019-01-22 15:00 ` Greg KH
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=20190122150048.GA11466@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=abailon@baylibre.com \
--cc=amit.kucheria@linaro.org \
--cc=andy.gross@linaro.org \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@linaro.org \
--cc=daidavid1@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=evgreen@chromium.org \
--cc=georgi.djakov@linaro.org \
--cc=henryc.chen@mediatek.com \
--cc=khilman@baylibre.com \
--cc=ksitaraman@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=maxime.ripard@bootlin.com \
--cc=mturquette@baylibre.com \
--cc=olof@lixom.net \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=sanjayc@nvidia.com \
--cc=seansw@qti.qualcomm.com \
--cc=skannan@codeaurora.org \
--cc=thierry.reding@gmail.com \
--cc=vincent.guittot@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 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.