From: Sagar Kadam <sagar.kadam@sifive.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, peter@korsgaard.com,
Palmer Dabbelt <palmer@sifive.com>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Linux I2C <linux-i2c@vger.kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH v6 1/3] dt-bindings: i2c: extend existing opencore bindings.
Date: Wed, 22 May 2019 10:21:47 +0530 [thread overview]
Message-ID: <CAARK3HmAYjnBH6Aa_R_uKQPs5JAdBAEt1=dvPz1mLmGaKKpP9w@mail.gmail.com> (raw)
In-Reply-To: <20190521135625.GN22024@lunn.ch>
Hi Andrew,
On Tue, May 21, 2019 at 7:26 PM Andrew Lunn <andrew@lunn.ch> wrote:
>
> > Required properties:
> > -- compatible : "opencores,i2c-ocores" or "aeroflexgaisler,i2cmst"
> > +- compatible : "opencores,i2c-ocores",
> > + "aeroflexgaisler,i2cmst",
> > + "sifive,fu540-c000-i2c","sifive,i2c0".
> > + For Opencore based I2C IP block reimplemented in
>
> It looks like there are some tabs vs space issues here.
Ohh. It was not catched in checkpatch.pl. I will update it.
Thanks,
Sagar Kadam
> Andrew
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-05-22 4:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 13:32 [PATCH v6 0/3] Extend dt bindings to support I2C on sifive devices and a fix broken IRQ in polling mode Sagar Shrikant Kadam
2019-05-21 13:32 ` [PATCH v6 1/3] dt-bindings: i2c: extend existing opencore bindings Sagar Shrikant Kadam
2019-05-21 13:56 ` Andrew Lunn
2019-05-22 4:51 ` Sagar Kadam [this message]
2019-05-21 13:32 ` [PATCH v6 2/3] i2c-ocores: sifive: add support for i2c device on FU540-c000 SoC Sagar Shrikant Kadam
2019-05-21 13:32 ` [PATCH v6 3/3] i2c-ocores: sifive: add polling mode workaround for FU540-C000 SoC Sagar Shrikant Kadam
2019-05-21 13:54 ` Andrew Lunn
2019-05-22 4:58 ` Sagar Kadam
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='CAARK3HmAYjnBH6Aa_R_uKQPs5JAdBAEt1=dvPz1mLmGaKKpP9w@mail.gmail.com' \
--to=sagar.kadam@sifive.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=peter@korsgaard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).