From: gregkh@linuxfoundation.org (Greg Kroah-Hartman)
To: linux-arm-kernel@lists.infradead.org
Subject: what's the next LTSI kernel version for long-term support
Date: Mon, 25 Feb 2013 22:21:37 -0800 [thread overview]
Message-ID: <20130226062137.GA25638@kroah.com> (raw)
In-Reply-To: <CAGsJ_4xxdcLPbKsOHXaADYzKRNeWq=n-jgoHYRMOXAqGPuyQ0w@mail.gmail.com>
On Tue, Feb 26, 2013 at 01:36:09PM +0800, Barry Song wrote:
> Hi Greg,
>
> 2013/2/26 Greg Kroah-Hartman <gregkh@linuxfoundation.org>:
> > On Tue, Feb 26, 2013 at 11:46:04AM +0800, Barry Song wrote:
> >> 2013/2/26 Greg Kroah-Hartman <gregkh@linuxfoundation.org>:
> >> > On Tue, Feb 26, 2013 at 11:06:56AM +0800, Barry Song wrote:
> >> >> Hi Greg/All,
> >> >> we have seen 3.4 was announced to be an LTSI in Aug, 2012. I'd like to
> >> >> know what is the next LTSI version since we might want to align our
> >> >> next release with LTSI.
> >> >
> >> > Who is "we" here?
> >> >
> >> people.
> >
> > I don't take anonymous "we want this" requests serious at all, sorry.
> > Please provide details as you are asking me to do work for you, right?
> >
>
> i just want to get some generic information not specific to any SoC
> vendor at all :-)
Then my generic response is going to be, "It will be announced when it
will be announced."
sorry,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Barry Song <21cnbao@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-arm-kernel@lists.infradead.org,
LKML <linux-kernel@vger.kernel.org>,
Binghua Duan <Binghua.Duan@csr.com>
Subject: Re: what's the next LTSI kernel version for long-term support
Date: Mon, 25 Feb 2013 22:21:37 -0800 [thread overview]
Message-ID: <20130226062137.GA25638@kroah.com> (raw)
In-Reply-To: <CAGsJ_4xxdcLPbKsOHXaADYzKRNeWq=n-jgoHYRMOXAqGPuyQ0w@mail.gmail.com>
On Tue, Feb 26, 2013 at 01:36:09PM +0800, Barry Song wrote:
> Hi Greg,
>
> 2013/2/26 Greg Kroah-Hartman <gregkh@linuxfoundation.org>:
> > On Tue, Feb 26, 2013 at 11:46:04AM +0800, Barry Song wrote:
> >> 2013/2/26 Greg Kroah-Hartman <gregkh@linuxfoundation.org>:
> >> > On Tue, Feb 26, 2013 at 11:06:56AM +0800, Barry Song wrote:
> >> >> Hi Greg/All,
> >> >> we have seen 3.4 was announced to be an LTSI in Aug, 2012. I'd like to
> >> >> know what is the next LTSI version since we might want to align our
> >> >> next release with LTSI.
> >> >
> >> > Who is "we" here?
> >> >
> >> people.
> >
> > I don't take anonymous "we want this" requests serious at all, sorry.
> > Please provide details as you are asking me to do work for you, right?
> >
>
> i just want to get some generic information not specific to any SoC
> vendor at all :-)
Then my generic response is going to be, "It will be announced when it
will be announced."
sorry,
greg k-h
next prev parent reply other threads:[~2013-02-26 6:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 3:06 what's the next LTSI kernel version for long-term support Barry Song
2013-02-26 3:06 ` Barry Song
2013-02-26 3:35 ` Greg Kroah-Hartman
2013-02-26 3:35 ` Greg Kroah-Hartman
2013-02-26 3:46 ` Barry Song
2013-02-26 3:46 ` Barry Song
2013-02-26 3:55 ` Greg Kroah-Hartman
2013-02-26 3:55 ` Greg Kroah-Hartman
2013-02-26 5:36 ` Barry Song
2013-02-26 5:36 ` Barry Song
2013-02-26 6:21 ` Greg Kroah-Hartman [this message]
2013-02-26 6:21 ` Greg Kroah-Hartman
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=20130226062137.GA25638@kroah.com \
--to=gregkh@linuxfoundation.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.