linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Jan 25
Date: Mon, 25 Jan 2016 19:50:38 +1100	[thread overview]
Message-ID: <20160125195038.55a375c8@canb.auug.org.au> (raw)
In-Reply-To: <20160125131141.41364cf5@canb.auug.org.au>

Hi all,

On Mon, 25 Jan 2016 13:11:41 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> On Mon, 25 Jan 2016 12:32:48 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Please do not add any material for v4.6 to your linux-next included
> > branches until after v4.5-rc1 is released.  
> 
> It has been pointed out that this is no longer relevant.
> 
> > Changes since 20160122:  
> 
> Also, I forgot to mention that my fixes tree contains this:
> 
> 	next: suppress the building of all the sound codecs on PPC for now

Also, there will be no linux-next release tomorrow.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

  reply	other threads:[~2016-01-25  8:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25  1:32 linux-next: Tree for Jan 25 Stephen Rothwell
2016-01-25  2:11 ` Stephen Rothwell
2016-01-25  8:50   ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-25  3:43 Stephen Rothwell
2023-01-25  3:37 Stephen Rothwell
2022-01-25  5:09 Stephen Rothwell
2021-01-25  9:14 Stephen Rothwell
2019-01-25  4:35 Stephen Rothwell
2017-01-25  5:49 Stephen Rothwell
2013-01-25  5:26 Stephen Rothwell
2012-01-25  3:19 Stephen Rothwell

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=20160125195038.55a375c8@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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).