From: Shawn Guo <shawnguo@kernel.org>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Jon Nettleton <jon@solid-run.com>,
Rabeeh Khoury <rabeeh@solid-run.com>,
Rob Herring <robh+dt@kernel.org>, Li Yang <leoyang.li@nxp.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] arm64: dts: lx2160a: add MDIO descriptions
Date: Mon, 23 Dec 2019 09:41:02 +0800 [thread overview]
Message-ID: <20191223014101.GC11523@dragon> (raw)
In-Reply-To: <20191216123442.GG25745@shell.armlinux.org.uk>
On Mon, Dec 16, 2019 at 12:34:42PM +0000, Russell King - ARM Linux admin wrote:
> Okay, I finally found it at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git/patch/?id=6e1b8fae892daa7ffb48570264b8e43b3f807e9a
>
> Note that that was unnecessarily difficult - google was unable to find
> it. Ioana's patch should have been copied to linux-arm-kernel as per
> MAINTAINERS, but wasn't. Is copying the appropriate mailing lists for
> a patch now optional?
Absolutely no. I will remind people to copy appropriate mailing lists
when sending patches. Sorry.
Shawn
next prev parent reply other threads:[~2019-12-23 1:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 12:00 [PATCH 0/2] Add support for Solidrun CEX7 platforms Russell King - ARM Linux admin
2019-12-09 12:00 ` [PATCH 1/2] arm64: dts: lx2160a: add MDIO descriptions Russell King
2019-12-11 7:33 ` Shawn Guo
2019-12-16 11:02 ` Russell King - ARM Linux admin
2019-12-16 11:34 ` Russell King - ARM Linux admin
2019-12-16 12:34 ` Russell King - ARM Linux admin
2019-12-23 1:41 ` Shawn Guo [this message]
2019-12-09 12:00 ` [PATCH 2/2] arm64: dts: lx2160a: add dts for CEX7 platforms Russell King
2019-12-11 7:40 ` Shawn Guo
2019-12-16 11:01 ` Russell King - ARM Linux admin
2019-12-23 2:19 ` Shawn Guo
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=20191223014101.GC11523@dragon \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jon@solid-run.com \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=rabeeh@solid-run.com \
--cc=robh+dt@kernel.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).