linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux-Next <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Jan 21
Date: Wed, 21 Jan 2015 12:08:05 +0100	[thread overview]
Message-ID: <CAMuHMdXuO+tYjSSnxg+B26MbiXiG-1mmFZ+=rx+OsxnnSPbcnA@mail.gmail.com> (raw)
In-Reply-To: <20150121192608.61062b6a@canb.auug.org.au>

Hi Stephen,

On Wed, Jan 21, 2015 at 9:26 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Removed trees: (not updated for more that 1 year)
>         configfs
>         cpupowerutils
>         dwmw2
>         embedded
>         ep93xx
>         fbdev
>         firmware
>         fsnotify
>         fw-nohz
>         hwspinlock
>         input-mt
>         ixp4xx
>         kconfig
>         logfs
>         lzo-update
>         md-current
>         msm
>         omfs
>         openrisc
>         oprofile
>         parisc
>         pcmcia
>         signal
>         sysctl
>         uclinux
>         uml
>         uprobes
>         viafb
>         writeback

Have you informed the corresponding maintainers?
Especially architecture-specific trees like openrisc and parisc may still
be (somewhat) active.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2015-01-21 11:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-21  8:26 linux-next: Tree for Jan 21 Stephen Rothwell
2015-01-21 11:08 ` Geert Uytterhoeven [this message]
2015-01-21 12:05   ` Geert Uytterhoeven
  -- strict thread matches above, loose matches on Subject: below --
2022-01-21  1:19 Stephen Rothwell
2021-01-21  7:28 Stephen Rothwell
2020-01-21  6:52 Stephen Rothwell
2019-01-21  5:26 Stephen Rothwell
2016-01-21  2:53 Stephen Rothwell
2014-01-21  6:30 Stephen Rothwell
2013-01-21  6:18 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='CAMuHMdXuO+tYjSSnxg+B26MbiXiG-1mmFZ+=rx+OsxnnSPbcnA@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).