From: Michal Simek <michal.simek@xilinx.com>
To: Jens Axboe <axboe@kernel.dk>, Davidlohr Bueso <dave@stgolabs.net>,
"Michal Simek" <michal.simek@xilinx.com>
Cc: devicetree@vger.kernel.org, monstr@monstr.eu,
YueHaibing <yuehaibing@huawei.com>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
linux-block@vger.kernel.org,
Chris Packham <chris.packham@alliedtelesis.co.nz>,
Paul Mackerras <paulus@samba.org>,
git@xilinx.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] xsysace: Remove SYSACE driver
Date: Tue, 23 Mar 2021 17:25:00 +0100 [thread overview]
Message-ID: <9c4911e6-92dc-0a0f-2f81-7d23e268144f@xilinx.com> (raw)
In-Reply-To: <6948510c-dc7e-d74a-62e3-e42be14cff16@kernel.dk>
On 3/23/21 5:23 PM, Jens Axboe wrote:
> On 3/22/21 6:04 PM, Davidlohr Bueso wrote:
>> Hi,
>>
>> On Mon, 09 Nov 2020, Michal Simek wrote:
>>
>>> Sysace IP is no longer used on Xilinx PowerPC 405/440 and Microblaze
>>> systems. The driver is not regularly tested and very likely not working for
>>> quite a long time that's why remove it.
>>
>> Is there a reason this patch was never merged? can the driver be
>> removed? I ran into this as a potential tasklet user that can be
>> replaced/removed.
>
> I'd be happy to merge it for 5.13.
>
Can you just take this version? Or do you want me to send it again?
Thanks,
Michal
next prev parent reply other threads:[~2021-03-23 16:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 10:59 [PATCH] xsysace: Remove SYSACE driver Michal Simek
2021-03-23 0:04 ` Davidlohr Bueso
2021-03-23 16:23 ` Jens Axboe
2021-03-23 16:25 ` Michal Simek [this message]
2021-03-23 16:28 ` Jens Axboe
2021-03-23 16:28 ` Michal Simek
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=9c4911e6-92dc-0a0f-2f81-7d23e268144f@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=axboe@kernel.dk \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=dave@stgolabs.net \
--cc=devicetree@vger.kernel.org \
--cc=git@xilinx.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=monstr@monstr.eu \
--cc=paulus@samba.org \
--cc=robh+dt@kernel.org \
--cc=yuehaibing@huawei.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;
as well as URLs for NNTP newsgroup(s).