public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Alex Deucher <alexdeucher@gmail.com>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	Christian Brauner <christian@brauner.io>,
	Christoph Hellwig <hch@lst.de>,
	Daniel Walker <dwalker@fifo99.com>,
	David Miller <davem@davemloft.net>,
	Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
	Felipe Balbi <balbi@kernel.org>, Lee Jones <lee@kernel.org>,
	Ley Foon Tan <lftan@altera.com>,
	Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
	Matthew Wilcox <willy@infradead.org>,
	Mimi Zohar <zohar@linux.vnet.ibm.com>,
	Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
	Rich Felker <dalias@libc.org>,
	Santosh Shilimkar <santosh.shilimkar@oracle.com>,
	Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: 1394 <linux1394-devel@lists.sourceforge.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: old trees removed from linux-next
Date: Thu, 5 Jan 2023 09:55:06 +1100	[thread overview]
Message-ID: <20230105095506.69ff567a@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]

Hi all,

The following trees have been removed form linux-next today as they
have not been updated for more than a year.  If you would like your tree
reinstated, please just let me know.

Each trees is followed by a list of commits in that tree that have not
been merged into Linus Torvald's tree (if any).

Tree			Last commit date
----			----------------
actions			2021-04-01 11:08:21 +0530
amdgpu-fixes		2019-11-06 22:06:23 -0500
cisco			2019-03-17 14:22:26 -0700
folio-iomap		2021-12-21 13:51:08 -0500
gpio-sim		2021-12-05 14:08:22 -0800
i3c-fixes		2021-02-28 16:05:19 -0800
ieee1394		2021-07-05 22:23:15 +0200
init			2020-07-31 08:16:01 +0200
integrity-fixes		2020-05-14 19:55:54 -0400
keystone		2021-08-10 15:52:26 -0700
mfd-fixes		2021-03-23 09:14:12 +0000
nios2			2021-02-19 15:02:09 +0800
pidfd-fixes		2021-04-02 14:11:10 +0200
raspberrypi		2021-12-18 18:53:04 +0100
  b4a213c53eed ("ARM: dts: bcm2711-rpi-400: Fix GPIO expander labels")
sh			2021-10-27 16:56:34 -0400
sparc-next		2020-06-22 09:49:59 -0700
usb-gadget		2021-04-04 14:15:36 -0700
usb-gadget-fixes	2021-04-04 14:15:36 -0700

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2023-01-04 22:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04 22:55 Stephen Rothwell [this message]
2023-01-06 11:42 ` linux-next: old trees removed from linux-next Alexandre Belloni

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=20230105095506.69ff567a@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=alexandre.belloni@bootlin.com \
    --cc=alexdeucher@gmail.com \
    --cc=balbi@kernel.org \
    --cc=brgl@bgdev.pl \
    --cc=christian@brauner.io \
    --cc=dalias@libc.org \
    --cc=davem@davemloft.net \
    --cc=dmitry.kasatkin@gmail.com \
    --cc=dwalker@fifo99.com \
    --cc=hch@lst.de \
    --cc=lee@kernel.org \
    --cc=lftan@altera.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=nsaenzjulienne@suse.de \
    --cc=santosh.shilimkar@oracle.com \
    --cc=stefanr@s5r6.in-berlin.de \
    --cc=willy@infradead.org \
    --cc=zohar@linux.vnet.ibm.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