From: Stephen Boyd <sboyd@codeaurora.org>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org,
robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
devicetree@vger.kernel.org, nm@ti.com
Subject: Re: [PATCH 0/5] ks8851 DT updates
Date: Fri, 23 May 2014 12:34:01 -0700 [thread overview]
Message-ID: <537FA2A9.6050309@codeaurora.org> (raw)
In-Reply-To: <20140523.151502.1106354754894891974.davem@davemloft.net>
On 05/23/14 12:15, David Miller wrote:
> From: Stephen Boyd <sboyd@codeaurora.org>
> Date: Thu, 22 May 2014 14:00:08 -0700
>
>> This set of patches properly documents the micrel ks8851 spi ethernet
>> controller, converts to devm_regulator_get_optional() to make error
>> paths slightly simpler, and finally adds supports for another
>> optional regulator and a reset gpio.
> Please do not submit patch sets that you expect different trees to
> integrate, this is painful for maintainers to deal with.
>
> Instead, submit the changes separately. One series for one
> maintainer's tree, another for the other maintainer's tree.
>
Ok. Shall I resend this series with the proper separation? Or can you
ignore the first patch? There isn't any functional dependency, more just
a checkpatch dependency which is not really all that important.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
WARNING: multiple messages have this Message-ID (diff)
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] ks8851 DT updates
Date: Fri, 23 May 2014 12:34:01 -0700 [thread overview]
Message-ID: <537FA2A9.6050309@codeaurora.org> (raw)
In-Reply-To: <20140523.151502.1106354754894891974.davem@davemloft.net>
On 05/23/14 12:15, David Miller wrote:
> From: Stephen Boyd <sboyd@codeaurora.org>
> Date: Thu, 22 May 2014 14:00:08 -0700
>
>> This set of patches properly documents the micrel ks8851 spi ethernet
>> controller, converts to devm_regulator_get_optional() to make error
>> paths slightly simpler, and finally adds supports for another
>> optional regulator and a reset gpio.
> Please do not submit patch sets that you expect different trees to
> integrate, this is painful for maintainers to deal with.
>
> Instead, submit the changes separately. One series for one
> maintainer's tree, another for the other maintainer's tree.
>
Ok. Shall I resend this series with the proper separation? Or can you
ignore the first patch? There isn't any functional dependency, more just
a checkpatch dependency which is not really all that important.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2014-05-23 19:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 21:00 [PATCH 0/5] ks8851 DT updates Stephen Boyd
2014-05-22 21:00 ` Stephen Boyd
2014-05-22 21:00 ` [PATCH 1/5] devicetree: bindings: Document micrel vendor prefix Stephen Boyd
2014-05-22 21:00 ` Stephen Boyd
2014-05-22 21:00 ` Stephen Boyd
2014-05-28 16:18 ` Rob Herring
2014-05-28 16:18 ` Rob Herring
2014-05-22 21:00 ` [PATCH 2/5] devicetree: bindings: Properly document micrel ks8851 SPI chips Stephen Boyd
2014-05-22 21:00 ` Stephen Boyd
2014-05-22 21:00 ` Stephen Boyd
2014-05-22 21:00 ` [PATCH 3/5] net: ks8851: Use devm_regulator_get_optional() Stephen Boyd
2014-05-22 21:00 ` Stephen Boyd
2014-05-22 21:00 ` [PATCH 4/5] net: ks8851: Add optional vdd_io regulator and reset gpio Stephen Boyd
2014-05-22 21:00 ` Stephen Boyd
2014-05-22 21:00 ` Stephen Boyd
2014-05-22 21:00 ` [PATCH 5/5] net: ks8851: Add of match table Stephen Boyd
2014-05-22 21:00 ` Stephen Boyd
2014-05-22 21:00 ` Stephen Boyd
2014-05-23 19:15 ` [PATCH 0/5] ks8851 DT updates David Miller
2014-05-23 19:15 ` David Miller
2014-05-23 19:34 ` Stephen Boyd [this message]
2014-05-23 19:34 ` Stephen Boyd
2014-05-23 19:37 ` David Miller
2014-05-23 19:37 ` David Miller
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=537FA2A9.6050309@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=nm@ti.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.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.