From: Sebastian Reichel <sre@debian.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Linus Walleij" <linus.walleij@linaro.org>,
"Shubhrajyoti Datta" <omaplinuxkernel@gmail.com>,
"Carlos Chinea" <cch.devel@gmail.com>,
"Paul Walmsley" <paul@pwsan.com>,
"Kevin Hilman" <khilman@deeprootsystems.com>,
"Russell King" <linux@arm.linux.org.uk>,
"Grant Likely" <grant.likely@linaro.org>,
"Rob Herring" <rob.herring@calxeda.com>,
"Pawel Moll" <pawel.moll@arm.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"Stephen Warren" <swarren@wwwdotorg.org>,
"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
"Rob Landley" <rob@landley.net>,
"'Benoît Cousson'" <bcousson@baylibre.com>,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
"'Pali Rohár'" <pali.rohar@gmail.com>,
"'Ивайло Димитров'" <freemangordon@abv.bg>
Subject: Re: [RFCv3 0/7] OMAP SSI driver
Date: Thu, 10 Oct 2013 19:21:30 +0200 [thread overview]
Message-ID: <20131010172128.GF28657@earth.universe> (raw)
In-Reply-To: <20131008172815.GA8313@atomide.com>
[-- Attachment #1: Type: text/plain, Size: 1929 bytes --]
Hi,
On Tue, Oct 08, 2013 at 10:28:15AM -0700, Tony Lindgren wrote:
> * Sebastian Reichel <sre@debian.org> [131006 13:36]:
> > Here is the third round of the OMAP SSI driver patches.
>
> Thanks for updating these, they look good to me now:
>
> Acked-by: Tony Lindgren <tony@atomide.com>
Ok. I guess it's time to check how this gets included in the kernel.
The first patch has already been queued and the last patch could
probably go through Benoît once the DT people have reviewed the
updated patches. The other ones would normally go through the
hsi tree, but that one was maintained by Carlos Chinea and is
now more or less orphaned.
My suggestion is:
1. I create another patch, which adds entries for hsi subsystem and
ssi driver to MAINTAINERS.
It would be nice to have some co-maintainers for the subsystem.
Linus Walleij maybe? I think you created the launchpad blueprint [1]?
Especially because I have no documentation/specification for HSI, which
brings me to my next slightly off topic request.
I would like to have access to SSI documentation and HSI specification.
Can the guys from Texas Instruments please give me some pointers how I
can get access to the NDA'd documentation? I couldn't find any hints
on ti.com.
2. I create a patch adding Carlos Chinea to CREDITS
3. I create a git repository and put all of the patches in there, so
that they can be pulled into linux-next.
4. I add a gpg/pgp signed tag with the key used to signed this mail.
Any issues with this or any other suggestions how to proceed? And if following this
- should I request an account on kernel.org to host the repository there,
or should I just upload it at a random place?
[0] https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/tree/Next/Trees
[1] https://blueprints.launchpad.net/linux-linaro/+spec/hsi-subsystem-maint
-- Sebastian
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-10-10 17:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-06 20:27 [RFCv3 0/7] OMAP SSI driver Sebastian Reichel
2013-10-06 20:27 ` [RFCv3 1/7] ARM: OMAP2+: hwmod-data: Add SSI information Sebastian Reichel
2013-10-09 5:43 ` Paul Walmsley
2013-10-10 14:19 ` Sebastian Reichel
2013-10-06 20:27 ` [RFCv3 2/7] HSI: add Device Tree support for HSI clients Sebastian Reichel
2013-10-06 20:27 ` [RFCv3 3/7] HSI: method to unregister clients from an hsi port Sebastian Reichel
2013-10-06 20:27 ` [RFCv3 4/7] HSI: hsi-char: add Device Tree support Sebastian Reichel
2013-10-06 20:27 ` [RFCv3 5/7] HSI: hsi-char: fix driver for multiport scenarios Sebastian Reichel
2013-10-06 20:27 ` [RFCv3 6/7] ARM: OMAP2+: HSI: Introduce OMAP SSI driver Sebastian Reichel
2013-10-06 20:27 ` [RFCv3 7/7] ARM: dts: N900: Add SSI information Sebastian Reichel
2013-10-22 12:48 ` Benoit Cousson
2013-10-22 14:44 ` Sebastian Reichel
2013-10-22 15:26 ` Benoit Cousson
[not found] ` <1381091235-18293-1-git-send-email-sre-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2013-10-08 17:28 ` [RFCv3 0/7] OMAP SSI driver Tony Lindgren
2013-10-10 17:21 ` Sebastian Reichel [this message]
2013-10-10 17:32 ` Tony Lindgren
2013-10-10 18:28 ` Aaro Koskinen
2013-10-10 20:02 ` Sebastian Reichel
2013-10-10 20:19 ` Aaro Koskinen
2013-10-10 22:22 ` Sebastian Reichel
2013-10-24 8:27 ` Pavel Machek
[not found] ` <20131010200236.GA6603-SfvFxonMDyemK9LvCR3Hrw@public.gmane.org>
2013-10-24 8:27 ` Pavel Machek
2013-10-24 8:27 ` Pavel Machek
2013-10-24 8:27 ` Pavel Machek
2013-10-24 8:27 ` Pavel Machek
2013-10-11 8:06 ` Linus Walleij
2013-10-21 9:23 ` Sebastian Reichel
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=20131010172128.GF28657@earth.universe \
--to=sre@debian.org \
--cc=bcousson@baylibre.com \
--cc=cch.devel@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=freemangordon@abv.bg \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=khilman@deeprootsystems.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=omaplinuxkernel@gmail.com \
--cc=pali.rohar@gmail.com \
--cc=paul@pwsan.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=sfr@canb.auug.org.au \
--cc=swarren@wwwdotorg.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).