From: Nishanth Menon <nm@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Lokesh Vutla <lokeshvutla@ti.com>,
Tony Lindgren <tony@atomide.com>,
linux-omap <linux-omap@vger.kernel.org>,
Sekhar Nori <nsekhar@ti.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 1/2] ARM: DRA7: Add support for soc_is_dra74x() and soc_is_dra72x() variants
Date: Fri, 5 Sep 2014 13:14:13 -0500 [thread overview]
Message-ID: <5409FD75.3090407@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1409051803190.9444@utopia.booyaka.com>
On 09/05/2014 01:08 PM, Paul Walmsley wrote:
[...]
>> In the meanwhile, we will try to provide test logs that you may desire
>> for at least the platforms we have functioning and access to. please
>> feel free to request specific test vectors if you feel our coverage is
>> not good enough.
>
> Thanks. You've been showing a lot of great leadership in proactively
> posting test logs. What I'd suggest doing is to keep that up, and if
> possible, post one of the test reports for each patch series that's
> posted, if possible.
I do have automated scripts verifying various defconfigs on a daily
basis for linux-next and master tags..
https://github.com/nmenon/kernel-test-logs/ (based on each tag).
Every TI engineer does have access to these platforms as well as I do.
Realistically, few platforms do go offline and online as time goes on.
we will try to post test reports for each series as much as our TI
policies let us.
--
Regards,
Nishanth Menon
WARNING: multiple messages have this Message-ID (diff)
From: nm@ti.com (Nishanth Menon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] ARM: DRA7: Add support for soc_is_dra74x() and soc_is_dra72x() variants
Date: Fri, 5 Sep 2014 13:14:13 -0500 [thread overview]
Message-ID: <5409FD75.3090407@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1409051803190.9444@utopia.booyaka.com>
On 09/05/2014 01:08 PM, Paul Walmsley wrote:
[...]
>> In the meanwhile, we will try to provide test logs that you may desire
>> for at least the platforms we have functioning and access to. please
>> feel free to request specific test vectors if you feel our coverage is
>> not good enough.
>
> Thanks. You've been showing a lot of great leadership in proactively
> posting test logs. What I'd suggest doing is to keep that up, and if
> possible, post one of the test reports for each patch series that's
> posted, if possible.
I do have automated scripts verifying various defconfigs on a daily
basis for linux-next and master tags..
https://github.com/nmenon/kernel-test-logs/ (based on each tag).
Every TI engineer does have access to these platforms as well as I do.
Realistically, few platforms do go offline and online as time goes on.
we will try to post test reports for each series as much as our TI
policies let us.
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2014-09-05 18:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 4:53 [PATCH v2 0/2] ARM: DRA7: hwmod: Add dra74x and dra72x specific ocp interface lists Lokesh Vutla
2014-07-28 4:53 ` Lokesh Vutla
2014-07-28 4:53 ` [PATCH v2 1/2] ARM: DRA7: Add support for soc_is_dra74x() and soc_is_dra72x() variants Lokesh Vutla
2014-07-28 4:53 ` Lokesh Vutla
2014-07-28 5:29 ` Paul Walmsley
2014-07-28 5:29 ` Paul Walmsley
2014-07-28 5:34 ` Lokesh Vutla
2014-07-28 5:34 ` Lokesh Vutla
2014-08-27 17:16 ` Nishanth Menon
2014-08-27 17:16 ` Nishanth Menon
2014-08-28 6:19 ` Paul Walmsley
2014-08-28 6:19 ` Paul Walmsley
2014-08-28 12:01 ` Nishanth Menon
2014-08-28 12:01 ` Nishanth Menon
2014-09-05 18:08 ` Paul Walmsley
2014-09-05 18:08 ` Paul Walmsley
2014-09-05 18:14 ` Nishanth Menon [this message]
2014-09-05 18:14 ` Nishanth Menon
2014-11-04 15:02 ` public trm am572x (was Re: Re: [PATCH v2 1/2] ARM: DRA7: Add support for soc_is_dra74x() and soc_is_dra72x() variants) Nishanth Menon
2014-11-04 15:02 ` Nishanth Menon
2014-07-28 4:53 ` [PATCH v2 2/2] ARM: DRA7: hwmod: Add dra74x and dra72x specific ocp interface lists Lokesh Vutla
2014-07-28 4:53 ` Lokesh Vutla
2014-07-28 5:31 ` Paul Walmsley
2014-07-28 5:31 ` Paul Walmsley
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=5409FD75.3090407@ti.com \
--to=nm@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=nsekhar@ti.com \
--cc=paul@pwsan.com \
--cc=tony@atomide.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 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.