From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kernel test robot <lkp@intel.com>,
"open list:BROADCOM NVRAM DRIVER" <linux-mips@vger.kernel.org>,
linux-iio <linux-iio@vger.kernel.org>,
bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>
Subject: Re: [PATCH v4] mips: bcm63xx: add support for clk_get_parent()
Date: Mon, 15 Nov 2021 12:56:14 +0200 [thread overview]
Message-ID: <CAHp75Vegc9bskv6DccJCBe1aYjB3mmqQHRbtD0vvYf_oxKi3eg@mail.gmail.com> (raw)
In-Reply-To: <20211115004218.13034-1-rdunlap@infradead.org>
On Mon, Nov 15, 2021 at 2:42 AM Randy Dunlap <rdunlap@infradead.org> wrote:
Just couple of side notes on the same topic (dropped people from Cc,
just MLs are left):
> Suggested-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
> Cc: Jonathan Cameron <jic23@kernel.org>
> Cc: Andy Shevchenko <andy.shevchenko@gmail.com>
> Cc: Russell King <linux@armlinux.org.uk>
> Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
> Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> Acked-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
1/ `git format-patch`/`git send-email` will create the Cc list from
all known tags, hence no need to repeat people in Cc.
2/ Consider to use --cc and --to to avoid burden on the git history
(sometimes people want to see it on mobile devices).
For myself I wrote the script [1] to give me some smartness. Maybe you
can find some ideas inside its implementation.
[1]: https://github.com/andy-shev/home-bin-tools/blob/master/ge2maintainer.sh
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-11-15 11:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 0:42 [PATCH v4] mips: bcm63xx: add support for clk_get_parent() Randy Dunlap
2021-11-15 4:18 ` Florian Fainelli
2021-11-15 10:56 ` Andy Shevchenko [this message]
2021-11-16 6:19 ` Randy Dunlap
2021-11-16 8:46 ` Thomas Bogendoerfer
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=CAHp75Vegc9bskv6DccJCBe1aYjB3mmqQHRbtD0vvYf_oxKi3eg@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=lkp@intel.com \
--cc=rdunlap@infradead.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).