From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: removed trees
Date: Mon, 5 Jul 2021 22:09:35 +0200 [thread overview]
Message-ID: <20210705220935.4d24a7af@kant> (raw)
In-Reply-To: <20210705215743.40b26667@kant>
[-- Attachment #1: Type: text/plain, Size: 858 bytes --]
On Jul 05 Stefan Richter wrote:
> On May 14 Stephen Rothwell wrote:
> > 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
>
> Would you be OK with adding linux1394.git (for-next branch) back to
> linux-next? There are two patches queued and I am finally aiming to get
> them merged. :-)
(PS, this is for the /next/ merge window after 5.14 is final, not for the
current window anymore of course.)
--
Stefan Richter
-======--=-= -=== --=-=
http://arcgraph.de/sr/
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-07-05 20:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 2:32 linux-next: removed trees Stephen Rothwell
2021-07-05 19:57 ` Stefan Richter
2021-07-05 20:09 ` Stefan Richter [this message]
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=20210705220935.4d24a7af@kant \
--to=stefanr@s5r6.in-berlin.de \
--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).