From: Greg KH <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
To: Paul Walmsley <pwalmsley-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
"stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [PATCH stable] ARM: tegra: unify Tegra's Kconfig a bit more
Date: Mon, 14 Oct 2013 11:20:06 -0700 [thread overview]
Message-ID: <20131014182006.GB18058@kroah.com> (raw)
In-Reply-To: <525C33D1.4080509-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
On Mon, Oct 14, 2013 at 11:11:29AM -0700, Paul Walmsley wrote:
> 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.
The -rc releases do not end up in a git tree, they show up in the
kernel.org/pub/linux/kernel/v3.0/stable-review/ directory when I
announce a -rc release is out for testing.
> Would this be something like applying the queue-* patches and
> testing on a nightly basis?
Yes, that is good to do as well, as that is what the -rc releases are
created from.
thanks,
greg k-h
next prev parent reply other threads:[~2013-10-14 18:20 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
[not found] ` <52525247.9060609-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-10-08 6:00 ` Paul Walmsley
[not found] ` <52539F98.2030307-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-10-10 23:11 ` Greg KH
[not found] ` <20131010231135.GF4301-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2013-10-14 18:00 ` Kevin Hilman
[not found] ` <87bo2r91hg.fsf-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2013-10-14 18:20 ` Greg KH
2013-10-14 18:11 ` Paul Walmsley
[not found] ` <525C33D1.4080509-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-10-14 18:20 ` Greg KH [this message]
[not found] ` <20131005233833.GA18223-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
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=20131014182006.GB18058@kroah.com \
--to=gregkh-hqyy1w1ycw8ekmwlsbkhg0b+6bgklq7r@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pwalmsley-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.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