From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Bartlomiej Zolnierkiewicz" <b.zolnierkie@samsung.com>,
"Scott Wood" <oss@buserror.net>, "Christoph Hellwig" <hch@lst.de>,
"Stefan Richter" <stefanr@s5r6.in-berlin.de>,
1394 <linux1394-devel@lists.sourceforge.net>,
"Theodore Ts'o" <tytso@mit.edu>,
"Andreas Färber" <afaerber@suse.de>,
"Zhang Rui" <rui.zhang@intel.com>,
"Eduardo Valentin" <edubezval@gmail.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Jason A. Donenfeld" <Jason@zx2c4.com>
Subject: linux-next: removed trees
Date: Fri, 14 May 2021 12:32:21 +1000 [thread overview]
Message-ID: <20210514123221.7c21393f@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 413 bytes --]
Hi all,
The following tree have been removed form linux-next because they have
not been updated in more than a year. If you want a tree reinstated,
just let me know.
fbdev
fsl
generic-ioremap
ieee1394
this contains the single commit
67f8e65e4fc1 firewire: net: remove set but not used variable 'guid'
random
realtek
thermal-rzhang
thermal-soc
y2038
zx2c4
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-05-14 2:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 2:32 Stephen Rothwell [this message]
2021-07-05 19:57 ` linux-next: removed trees Stefan Richter
2021-07-05 20:09 ` Stefan Richter
2021-07-06 12:33 ` Stephen Rothwell
2021-07-12 22:39 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2019-05-20 23:37 Stephen Rothwell
2019-05-21 8:10 ` David Howells
2019-05-21 13:03 ` Steven Rostedt
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=20210514123221.7c21393f@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=Jason@zx2c4.com \
--cc=afaerber@suse.de \
--cc=arnd@arndb.de \
--cc=b.zolnierkie@samsung.com \
--cc=edubezval@gmail.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=oss@buserror.net \
--cc=rui.zhang@intel.com \
--cc=stefanr@s5r6.in-berlin.de \
--cc=tytso@mit.edu \
/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.