public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dilip Kota <eswara.kota@linux.intel.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	kishon@ti.com, robh@kernel.org, andriy.shevchenko@intel.com,
	cheol.yong.kim@intel.com, chuanhua.lei@linux.intel.com,
	qi-ming.wu@intel.com, yixin.zhu@intel.com
Subject: Re: [PATCH v5 1/4] mfd: syscon: Add fwnode_to_regmap
Date: Thu, 16 Apr 2020 14:57:16 +0800	[thread overview]
Message-ID: <0adafade-7228-58d3-3db0-b06325712468@linux.intel.com> (raw)
In-Reply-To: <20200415093116.GH2167633@dell>


On 4/15/2020 5:31 PM, Lee Jones wrote:
> On Wed, 25 Mar 2020, Dilip Kota wrote:
>
>> Traverse regmap handle entry from firmware node handle.
>>
>> Signed-off-by: Dilip Kota <eswara.kota@linux.intel.com>
>> ---
>> Changes on v5:
>>    No changes
>>
>> Changes on v4:
>>    No changes
>>
>>   drivers/mfd/syscon.c       | 8 ++++++++
>>   include/linux/mfd/syscon.h | 6 ++++++
>>   2 files changed, 14 insertions(+)
> I think you'll find it very difficult to have a patch merged if you do
> not send it to any Maintainers of the associated subsystem(s).
Sorry, i completely missed adding the system configuration Maintainers. 
I was completely thinking about the PHY driver( in doing changes and 
upgrades) while sending the patches.
I have noticed it, and already sent v6 patch series by adding you and 
arnd@arndb.de

"[RESEND PATCH v6 0/4] Add Intel ComboPhy driver"
Snippet from the mail.

"Re-sending the patches v6 by adding the system configuration Maintainers,
which i missed to add them."

Regards,
Dilip

>
> Did you use `scripts/get_maintainer.pl` at all?
>

  reply	other threads:[~2020-04-16  6:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-25  8:59 [PATCH v5 0/4] Add Intel ComboPhy driver Dilip Kota
2020-03-25  8:59 ` [PATCH v5 1/4] mfd: syscon: Add fwnode_to_regmap Dilip Kota
2020-04-15  9:31   ` Lee Jones
2020-04-16  6:57     ` Dilip Kota [this message]
2020-04-16  7:18       ` Lee Jones
2020-03-25  8:59 ` [PATCH v5 2/4] dt-bindings: phy: Add PHY_TYPE_XPCS definition Dilip Kota
2020-03-31 21:23   ` Rob Herring
2020-03-25  8:59 ` [PATCH v5 3/4] dt-bindings: phy: Add YAML schemas for Intel ComboPhy Dilip Kota
2020-03-31 21:24   ` Rob Herring
2020-03-25  8:59 ` [PATCH v5 4/4] phy: intel: Add driver support for ComboPhy Dilip Kota

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=0adafade-7228-58d3-3db0-b06325712468@linux.intel.com \
    --to=eswara.kota@linux.intel.com \
    --cc=andriy.shevchenko@intel.com \
    --cc=cheol.yong.kim@intel.com \
    --cc=chuanhua.lei@linux.intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kishon@ti.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=qi-ming.wu@intel.com \
    --cc=robh@kernel.org \
    --cc=yixin.zhu@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox