From: Kuldeep Singh <singh.kuldeep87k@gmail.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
Scott Branden <sbranden@broadcom.com>,
Ray Jui <rjui@broadcom.com>
Subject: Re: [PATCH 1/3] MAINTAINERS: Update git tree for broadcom IPROC boards
Date: Tue, 8 Mar 2022 10:24:42 +0530 [thread overview]
Message-ID: <20220308045442.GA67274@9a2d8922b8f1> (raw)
In-Reply-To: <e08f2e52-0684-89b7-b1df-f27e4c0d74f2@gmail.com>
On Mon, Mar 07, 2022 at 11:19:20AM -0800, Florian Fainelli wrote:
> On 3/7/22 10:20 AM, Kuldeep Singh wrote:
> > Current git tree for broadcom boards is pretty outdated as it's not
> > updated for a long time. Fix the reference.
> >
> > Signed-off-by: Kuldeep Singh <singh.kuldeep87k@gmail.com>
>
> Applied to maintainers/next. Please use scripts/get_maintainers.pl next
> time though, our internal mailing list was not copied, thus our
> patchwork instance did not pick up the patch.
Ahh i see. Though I ran get_maintainers.pl, but couldn't cc internal mailing
list. I'll take care next time.
Thanks!
Regards
Kuldeep
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-03-08 4:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 18:20 [PATCH 1/3] MAINTAINERS: Update git tree for broadcom IPROC boards Kuldeep Singh
2022-03-07 18:21 ` [PATCH 2/3] arm64: dts: ns2: Fix spi clock name Kuldeep Singh
2022-03-07 19:19 ` Florian Fainelli
2022-03-07 18:21 ` [PATCH 3/3] arm64: dts: stingray: " Kuldeep Singh
2022-03-07 19:19 ` Florian Fainelli
2022-03-07 19:19 ` [PATCH 1/3] MAINTAINERS: Update git tree for broadcom IPROC boards Florian Fainelli
2022-03-08 4:54 ` Kuldeep Singh [this message]
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=20220308045442.GA67274@9a2d8922b8f1 \
--to=singh.kuldeep87k@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.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 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).