From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Vignesh Raghavendra <vigneshr@ti.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Miquel Raynal <miquel.raynal@bootlin.com>
Subject: Re: linux-next: branches to be removed
Date: Wed, 12 Jul 2023 14:44:24 +1000 [thread overview]
Message-ID: <20230712144424.57ab0009@canb.auug.org.au> (raw)
In-Reply-To: <40fad90a-551e-e66b-f225-8add53b417e0@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]
Hi Vignesh,
On Wed, 12 Jul 2023 09:28:41 +0530 Vignesh Raghavendra <vigneshr@ti.com> wrote:
>
> + Miquel
>
> On 10/07/23 12:56, Stephen Rothwell wrote:
> >
> > I will remove the following branches from linux-next tomorrow as they have
> > not been updated in over a year. If you want your branch retained or
> > reinstated, please just send me an email letting me know.
> >
>
> [...]
>
> > git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git cfi/next
>
> [...]
>
> > These branches are all empty except the last which just contains a
> > commit that is the same patch of a commit in Linus' tree.
> >
>
> Development on CFI + Hyperbus has slowed down a bit, apart from odd
> fixes every now and then which I have been asking Miquel to directly
> apply to mtd/fixes. I do expect odd patches/improvements over next few
> months, would it be possible to keep this tree included in linux-next if
> its not too much of a burden?
Done starting tomorrow.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2023-07-12 4:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 7:26 linux-next: branches to be removed Stephen Rothwell
2023-07-10 7:46 ` Florian Westphal
2023-07-10 8:40 ` Stephen Rothwell
2023-07-10 9:11 ` Miguel Ojeda
2023-07-10 8:22 ` Stephen Rothwell
2023-07-10 10:41 ` Miguel Ojeda
2023-07-10 15:07 ` Gabriel Krisman Bertazi
2023-07-10 22:59 ` Stephen Rothwell
2023-07-10 17:52 ` Vineet Gupta
2023-07-10 23:04 ` Stephen Rothwell
2023-07-12 3:58 ` Vignesh Raghavendra
2023-07-12 4:44 ` Stephen Rothwell [this message]
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=20230712144424.57ab0009@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=vigneshr@ti.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