All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Sinthu Raja M <sinthu.raja@mistralsolutions.com>
Cc: "Nagalla, Hari" <hnagalla@ti.com>,
	Ohad Ben-Cohen <ohad@wizery.com>,
	Rob Herring <robh+dt@kernel.org>, Suman Anna <s-anna@ti.com>,
	Mathieu Poirier <mathieu.poirier@linaro.org>,
	<linux-remoteproc@vger.kernel.org>,
	Device Tree Mailing List <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, Lokesh Vutla <lokeshvutla@ti.com>,
	Sinthu Raja <sinthu.raja@ti.com>
Subject: Re: [PATCH V1] dt-bindings: remoteproc: k3-dsp: Update example to remove board specific
Date: Fri, 20 Aug 2021 12:34:24 -0500	[thread overview]
Message-ID: <20210820173424.3cqqbhbw5cdmrbum@disrupt> (raw)
In-Reply-To: <CAEd-yTQgWLZUKPJQvByWfo3w=gNFLz=F6q6_oF_0WC7cRpZ6dw@mail.gmail.com>

On 11:56-20210820, Sinthu Raja M wrote:
[...]

> May I know to which commit I have to tag the Fixes. If you are

git blame Documentation/devicetree/bindings/remoteproc/ti,k3-dsp-rproc.yaml ?

Look at the commit that introduced the original code that you are
fixing. In this case, 2a2180206ab62 perhaps?

[...]
> It didn't catch in my basic patch verification. But the generated
> patch does have the From header, but sometimes the From header is
> getting truncated when submitting for review. Still working on that to
> fix it. (using Gmail client to submitting the patch)


https://www.kernel.org/doc/html/v4.11/process/email-clients.html

"Gmail (Web GUI)

Does not work for sending patches.
"


-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D

  reply	other threads:[~2021-08-20 17:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-18  7:40 [PATCH V1] dt-bindings: remoteproc: k3-dsp: Update example to remove board specific Sinthu Raja
2021-08-18 13:05 ` Nishanth Menon
2021-08-20  6:26   ` Sinthu Raja M
2021-08-20 17:34     ` Nishanth Menon [this message]
2021-08-18 17:03 ` Rob Herring

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=20210820173424.3cqqbhbw5cdmrbum@disrupt \
    --to=nm@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hnagalla@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=lokeshvutla@ti.com \
    --cc=mathieu.poirier@linaro.org \
    --cc=ohad@wizery.com \
    --cc=robh+dt@kernel.org \
    --cc=s-anna@ti.com \
    --cc=sinthu.raja@mistralsolutions.com \
    --cc=sinthu.raja@ti.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.