mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Adam Borowski <kilobyte@angband.pl>, akpm@linux-foundataion.org
Cc: linux-kernel@vger.kernel.org, andrew@lunn.ch,
	vivien.didelot@savoirfairelinux.com,
	adi-buildroot-devel@lists.sourceforge.net, realmz6@gmail.com
Subject: Re: [PATCH 0/2] blackfin: Remove dead DSA code
Date: Sun, 16 Jul 2017 08:59:53 -0700	[thread overview]
Message-ID: <be3ba66c-182b-8fc2-f9cf-57e200533013@gmail.com> (raw)
In-Reply-To: <20170530004544.y5mcgfwfoka4puvn@angband.pl>



On 05/29/2017 05:45 PM, Adam Borowski wrote:
> On Sun, May 28, 2017 at 04:59:47PM -0700, Florian Fainelli wrote:
>> Hello? anyone still maintaining blackfin here?
> 
> Looks like people edit arch/blackfin/ a lot whenever it interferes with some
> other work, but the only blackfin-specific fixes seem to be a couple of
> drive-by ones by Al Viro, then nothing until first half of 2015.
> 
> Last maintainer pull request: 668b54a1 on 2015-04-24.
> 
> There was some mailing list traffic in Jan 2016:
> https://sourceforge.net/p/adi-buildroot/mailman/adi-buildroot-devel/
> 
> So it looks pretty dead...

Yes indeed, Andrew, would you or someone else be willing to take these
two patches, or should we just remove blackfin entirely from the source
tree (there might still be active users).

Thanks!
-- 
Florian

  reply	other threads:[~2017-07-16 15:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-01 22:42 Florian Fainelli
2017-01-01 22:42 ` [PATCH 1/2] blackfin: tcm-bf518: Remove dsa.h inclusion Florian Fainelli
2017-01-01 22:42 ` [PATCH 2/2] blackfin: ezbrd: Remove non-functional DSA/KSZ8893M code Florian Fainelli
2017-01-29  3:15 ` [PATCH 0/2] blackfin: Remove dead DSA code Florian Fainelli
2017-05-28 23:59 ` Florian Fainelli
2017-05-30  0:45   ` Adam Borowski
2017-07-16 15:59     ` Florian Fainelli [this message]
2017-07-16 16:00       ` Florian Fainelli

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=be3ba66c-182b-8fc2-f9cf-57e200533013@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=adi-buildroot-devel@lists.sourceforge.net \
    --cc=akpm@linux-foundataion.org \
    --cc=andrew@lunn.ch \
    --cc=kilobyte@angband.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=realmz6@gmail.com \
    --cc=vivien.didelot@savoirfairelinux.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
all inboxes | Powered by JetHome®