From: pwalmsley@nvidia.com (Paul Walmsley)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH stable] ARM: tegra: unify Tegra's Kconfig a bit more
Date: Mon, 14 Oct 2013 11:11:29 -0700 [thread overview]
Message-ID: <525C33D1.4080509@nvidia.com> (raw)
In-Reply-To: <20131010231135.GF4301@kroah.com>
Hi Greg,
On 10/10/2013 04:11 PM, Greg KH wrote:
> On Mon, Oct 07, 2013 at 11:00:56PM -0700, Paul Walmsley wrote:
>
>> Well, here's a public link for it:
>>
>> http://nvt.pwsan.com/pub/linux-stable/testlogs/
>>
>> So far it's seeded with v3.11.[34]. It should update automatically
>> as new releases come out. So far the tests are quite basic (build +
>> boot to minimal userspace). Please let Stephen and I know if you
>> have any comments or suggestions.
> That's great to see. Testing the -rc stable releases would be great, to
> find if I break anything, as I don't have Tegra hardware to test them
> out on.
Could you point out the -rc stable releases that you're referring to?
Took a look at the linux-stable.git and stable-queue.git trees but was
unsure what matched that description.
Would this be something like applying the queue-* patches and testing on
a nightly basis?
- Paul
next prev parent reply other threads:[~2013-10-14 18:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-04 20:10 [PATCH stable] ARM: tegra: unify Tegra's Kconfig a bit more Stephen Warren
2013-10-05 23:38 ` Greg KH
2013-10-07 6:18 ` Paul Walmsley
2013-10-08 6:00 ` Paul Walmsley
2013-10-10 23:11 ` Greg KH
2013-10-14 18:00 ` Kevin Hilman
2013-10-14 18:20 ` Greg KH
2013-10-14 18:11 ` Paul Walmsley [this message]
2013-10-14 18:20 ` Greg KH
2013-10-07 16:47 ` Stephen Warren
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=525C33D1.4080509@nvidia.com \
--to=pwalmsley@nvidia.com \
--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 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).