From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] arm: spear6xx: DT cleanups and improvements
Date: Mon, 17 Apr 2017 09:36:55 +0530 [thread overview]
Message-ID: <20170417040655.GA28191@vireshk-i7> (raw)
In-Reply-To: <20170414224715.4493109a@free-electrons.com>
On 14-04-17, 22:47, Thomas Petazzoni wrote:
> Thanks! However, unless I'm missing something, I don't see these
> changes in linux-next. Who is going to apply them and send a pull
> request to arm-soc? You're listed as one the maintainers for SPEAr, so
> I was assuming you would do it. Is this correct?
>
> Let me know if there's anything to be done on my side to get those
> patches merged.
Yes, that would be the normal flow and I did that initially. But then the number
of patches really decreased and its better to send the patches directly to ARM
maintainers so that they can apply them. No need of PULL requests really.
Send them to: arm-soc <arm@kernel.org>
--
viresh
next prev parent reply other threads:[~2017-04-17 4:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 10:51 [PATCH v2 0/5] arm: spear6xx: DT cleanups and improvements Thomas Petazzoni
2017-03-21 10:51 ` [PATCH v2 1/5] arm: spear6xx: add labels to various nodes in spear600.dtsi Thomas Petazzoni
2017-03-21 10:51 ` [PATCH v2 2/5] arm: spear6xx: use node labels in spear600-evb.dts Thomas Petazzoni
2017-03-21 10:51 ` [PATCH v2 3/5] arm: spear6xx: fix spaces " Thomas Petazzoni
2017-03-21 10:51 ` [PATCH v2 4/5] arm: spear6xx: switch spear600-evb to the new flash partition DT binding Thomas Petazzoni
2017-03-21 10:51 ` [PATCH v2 5/5] arm: spear6xx: remove unneeded pinctrl properties in spear600-evb Thomas Petazzoni
2017-03-21 10:59 ` [PATCH v2 0/5] arm: spear6xx: DT cleanups and improvements Viresh Kumar
2017-04-14 20:47 ` Thomas Petazzoni
2017-04-17 4:06 ` Viresh Kumar [this message]
2017-04-17 7:10 ` Thomas Petazzoni
2017-04-17 7:13 ` Viresh Kumar
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=20170417040655.GA28191@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=linux-arm-kernel@lists.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 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.