public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Luke Yang <luke.adi@gmail.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
	Andrew Morton <akpm@osdl.org>,
	bunk@stusta.de, linux-kernel@vger.kernel.org
Subject: Re: ADI Blackfin patch for kernel 2.6.14
Date: Mon, 14 Nov 2005 20:14:18 -0800	[thread overview]
Message-ID: <20051115041418.GA20565@kroah.com> (raw)
In-Reply-To: <489ecd0c0511141840t4e7ba87ftfdba8c287063565f@mail.gmail.com>

On Tue, Nov 15, 2005 at 10:40:05AM +0800, Luke Yang wrote:
> On 11/14/05, Arjan van de Ven <arjan@infradead.org> wrote:
> >
> > > > The process is like maintaining any other part of the kernel:
> > > >   - Try to make sure it works on all releases (harder to do with a full
> > > >     arch, I know, but not impossible.)
> > >
> > >   Does this include all the rc releases? and the 2.6.14.x releases?
> > >
> > > >   - keep it up to date with bugfixes and the such
> > >
> > >   So the process is: when kernel release a new version, we should
> > > update our arch related files to the new kernel, then send you the
> > > patch. Am I right?
> >
> > well the idea is that you fix things BEFORE the kernel is released for
> > final, so that the final releases work out of the box (well out of
> > kernel.org). This implies that you sort of track the git tree on a
> > regular basis, but at minimum look at the first -rc kernel.
> 
>   yep, that's our plan. And for the 2.6.14.1, 2.6.14.2... versions, do
> we have to follow every of them?

They should hopefully _not_ break anything, due to the small size of
those releases.  If they do, please let the stable team know.

thanks,

greg k-h

  reply	other threads:[~2005-11-15  4:29 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-01  9:28 ADI Blackfin patch for kernel 2.6.14 Luke Yang
2005-11-01 16:51 ` Adrian Bunk
2005-11-02  7:06   ` Luke Yang
2005-11-04  4:59     ` Luke Yang
2005-11-04 23:06       ` Greg KH
2005-11-07  6:58         ` Luke Yang
2005-11-07 16:59           ` Greg KH
2005-11-08  7:50             ` Andrew Morton
2005-11-11 11:26               ` Luke Yang
2005-11-12 11:58                 ` Andrey Volkov
2005-11-14  7:22                   ` Luke Yang
2005-11-12 21:47                 ` Greg KH
2005-11-13 14:22                   ` Bernd Schmidt
2005-11-14  7:34                   ` Luke Yang
2005-11-14  7:52                     ` Arjan van de Ven
2005-11-15  2:40                       ` Luke Yang
2005-11-15  4:14                         ` Greg KH [this message]
2005-11-14 12:53                     ` Alan Cox
2005-11-16  3:44               ` Luke Yang
2005-11-16  6:11                 ` Paul Jackson
2005-11-16  6:34                   ` Luke Yang
2005-11-16 13:42               ` Bernd Schmidt
  -- strict thread matches above, loose matches on Subject: below --
2005-11-14 20:53 Robin Getz
2005-11-15 19:11 ` Matthieu CASTET
2005-11-17  5:38 Robin Getz

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=20051115041418.GA20565@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luke.adi@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox