From: Wolfram Sang <wsa@the-dreams.de>
To: Sagar Kadam <sagar.kadam@sifive.com>
Cc: Andrew Lunn <andrew@lunn.ch>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
peter@korsgaard.com, Palmer Dabbelt <palmer@sifive.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Linux I2C <linux-i2c@vger.kernel.org>,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 3/3] i2c-ocores: sifive: add polling mode workaround for FU540-C000 SoC.
Date: Thu, 23 May 2019 15:53:50 +0200 [thread overview]
Message-ID: <20190523135350.GA4985@kunai> (raw)
In-Reply-To: <CAARK3H=BPT3aGUGiQvov5aqFRNVTSeyqJ-bNGw6uEoU7c8iiJg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 225 bytes --]
> Ok, Great. Do we need to write to him about this patchset?
Nope. Hint: You can dig in the mail archives studying older patches to
see how things work. I do this as well because things may work
differently per subsystem.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@the-dreams.de>
To: Sagar Kadam <sagar.kadam@sifive.com>
Cc: Mark Rutland <mark.rutland@arm.com>, Andrew Lunn <andrew@lunn.ch>,
peter@korsgaard.com, devicetree@vger.kernel.org,
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 v7 3/3] i2c-ocores: sifive: add polling mode workaround for FU540-C000 SoC.
Date: Thu, 23 May 2019 15:53:50 +0200 [thread overview]
Message-ID: <20190523135350.GA4985@kunai> (raw)
In-Reply-To: <CAARK3H=BPT3aGUGiQvov5aqFRNVTSeyqJ-bNGw6uEoU7c8iiJg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 225 bytes --]
> Ok, Great. Do we need to write to him about this patchset?
Nope. Hint: You can dig in the mail archives studying older patches to
see how things work. I do this as well because things may work
differently per subsystem.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
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-23 13:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 8:59 [PATCH v7 0/3] Extend dt bindings to support I2C on sifive devices and a fix broken IRQ in polling mode Sagar Shrikant Kadam
2019-05-22 8:59 ` Sagar Shrikant Kadam
2019-05-22 8:59 ` [PATCH v7 1/3] dt-bindings: i2c: extend existing opencore bindings Sagar Shrikant Kadam
2019-05-22 8:59 ` Sagar Shrikant Kadam
2019-05-24 20:40 ` Rob Herring
2019-05-24 20:40 ` Rob Herring
2019-05-27 13:25 ` Sagar Kadam
2019-05-27 13:25 ` Sagar Kadam
2019-05-22 8:59 ` [PATCH v7 2/3] i2c-ocores: sifive: add support for i2c device on FU540-c000 SoC Sagar Shrikant Kadam
2019-05-22 8:59 ` Sagar Shrikant Kadam
2019-05-22 8:59 ` [PATCH v7 3/3] i2c-ocores: sifive: add polling mode workaround for FU540-C000 SoC Sagar Shrikant Kadam
2019-05-22 8:59 ` Sagar Shrikant Kadam
2019-05-22 19:45 ` Andrew Lunn
2019-05-22 19:45 ` Andrew Lunn
2019-05-22 19:45 ` Andrew Lunn
2019-05-23 5:17 ` Sagar Kadam
2019-05-23 12:34 ` Andrew Lunn
2019-05-23 12:34 ` Andrew Lunn
2019-05-23 12:34 ` Andrew Lunn
2019-05-23 13:43 ` Sagar Kadam
2019-05-23 13:43 ` Sagar Kadam
2019-05-23 13:53 ` Wolfram Sang [this message]
2019-05-23 13:53 ` Wolfram Sang
2019-05-24 5:05 ` Sagar Kadam
2019-05-24 5:05 ` 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=20190523135350.GA4985@kunai \
--to=wsa@the-dreams.de \
--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 \
--cc=sagar.kadam@sifive.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 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.