From: Rob Herring <robh@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
mturquette@baylibre.com, sboyd@kernel.org,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] devicetree: bindings: clock: Minor typo fix in the file armada3700-tbg-clock.txt
Date: Thu, 25 Mar 2021 18:20:46 -0600 [thread overview]
Message-ID: <20210326002046.GA2016315@robh.at.kernel.org> (raw)
In-Reply-To: <efc138db-d82d-a9f0-ca7b-61ae993e0459@infradead.org>
On Wed, Mar 17, 2021 at 01:12:28PM -0700, Randy Dunlap wrote:
> On 3/17/21 12:46 PM, Bhaskar Chowdhury wrote:
> > On 10:32 Wed 17 Mar 2021, Randy Dunlap wrote:
> >> On 3/17/21 3:08 AM, Bhaskar Chowdhury wrote:
> >>>
> >>> s/provde/provide/
> >>>
> >>> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
> >>
> >> Bhaskar,
> >>
> >> Did you send this one to "robh+dt@kernel.org"?
> >> AFAICT, it was sent to "dt@kernel.org", which bounces.
> >>
> >> If you used "robh+dt@kernel.org", it appears that 'get send-email' has a problem with that.
> >>
> > I sent out a mail to David and Rob, including you for the same problem . Hope
> > David will do something to change that address or Rob might do something . So
> > that it will not bounce in future.
>
> David said that vger isn't modifying the email address.
> And there is nothing wrong with it (robh+dt@kernel.org),
> although it appears that either git send-email or just gmail.com
> does not like it.
I've used that for years and never heard of any problems.
Rob
next prev parent reply other threads:[~2021-03-26 0:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 10:08 [PATCH] devicetree: bindings: clock: Minor typo fix in the file armada3700-tbg-clock.txt Bhaskar Chowdhury
2021-03-17 17:29 ` Randy Dunlap
2021-03-17 17:32 ` Randy Dunlap
2021-03-17 19:46 ` Bhaskar Chowdhury
2021-03-17 20:12 ` Randy Dunlap
2021-03-26 0:20 ` Rob Herring [this message]
2021-03-26 0:21 ` 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=20210326002046.GA2016315@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=rdunlap@infradead.org \
--cc=sboyd@kernel.org \
--cc=unixbhaskar@gmail.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.