From: Christoph Hellwig <hch@infradead.org>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: Tejun Heo <tj@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Michael Schmitz <schmitzmic@gmail.com>,
linux-ide@vger.kernel.org, linux-m68k@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] ata: allow subsystem to be used on m68k arch
Date: Fri, 30 Dec 2016 06:12:49 -0800 [thread overview]
Message-ID: <20161230141249.GA4543@infradead.org> (raw)
In-Reply-To: <1483106478-1382-2-git-send-email-b.zolnierkie@samsung.com>
On Fri, Dec 30, 2016 at 03:01:16PM +0100, Bartlomiej Zolnierkiewicz wrote:
> When libata was merged m68k lacked IOMAP support. This has not been
> true for a long time now so allow subsystem to be used on m68k.
Is that dependency needed at all anymore? What exact functionality
is missing on m32r and s390?
next prev parent reply other threads:[~2016-12-30 14:12 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20161230140139epcas5p160eda5a6a77be084e21f12002c85cc2a@epcas5p1.samsung.com>
2016-12-30 14:01 ` [PATCH 0/3] ata: add m68k/Atari Falcon PATA support Bartlomiej Zolnierkiewicz
[not found] ` <CGME20161230140141epcas5p161d9467e10e294f502863b5347e351d5@epcas5p1.samsung.com>
2016-12-30 14:01 ` [PATCH 1/3] ata: allow subsystem to be used on m68k arch Bartlomiej Zolnierkiewicz
2016-12-30 14:12 ` Christoph Hellwig [this message]
[not found] ` <CGME20161230171438epcas1p3c1d8ea8e4c77d796b81f7130c5e61d3f@epcas1p3.samsung.com>
2016-12-30 17:14 ` Bartlomiej Zolnierkiewicz
2017-01-08 10:08 ` Christoph Hellwig
[not found] ` <CGME20170109160128epcas1p36a0a8f79b32e5024ffa480fd848e3a79@epcas1p3.samsung.com>
2017-01-09 16:01 ` Bartlomiej Zolnierkiewicz
2017-01-09 16:15 ` Geert Uytterhoeven
[not found] ` <CGME20161230140144epcas1p2ada13244f4ba5b45ed903ab7d614f6db@epcas1p2.samsung.com>
2016-12-30 14:01 ` [PATCH 2/3] ata: pass queued command to ->sff_data_xfer method Bartlomiej Zolnierkiewicz
[not found] ` <CGME20161230140147epcas5p1fa7e99f39921a8ee90aabd59ff7b7645@epcas5p1.samsung.com>
2016-12-30 14:01 ` [PATCH 3/3] ata: add Atari Falcon PATA controller driver Bartlomiej Zolnierkiewicz
2017-01-03 10:49 ` [PATCH 0/3] ata: add m68k/Atari Falcon PATA support Geert Uytterhoeven
2017-01-09 16:11 ` Bartlomiej Zolnierkiewicz
2017-01-10 16:09 ` Tejun Heo
2017-01-05 21:01 ` Michael Schmitz
2017-01-10 12:53 ` Bartlomiej Zolnierkiewicz
2017-01-10 20:02 ` Michael Schmitz
2017-01-13 2:33 ` Finn Thain
2017-01-14 8:55 ` Michael Schmitz
2017-01-14 23:47 ` Finn Thain
2017-01-15 1:48 ` Michael Schmitz
2017-01-15 4:42 ` Finn Thain
2017-01-20 7:49 ` Michael Schmitz
2017-01-21 7:37 ` Finn Thain
2017-01-23 8:04 ` Michael Schmitz
2017-01-26 8:47 ` Finn Thain
2017-01-26 9:03 ` Geert Uytterhoeven
2017-01-27 1:41 ` Finn Thain
2017-01-27 4:28 ` Michael Schmitz
2017-02-01 8:40 ` Finn Thain
2017-02-01 8:45 ` Geert Uytterhoeven
2017-02-02 7:48 ` Michael Schmitz
2017-01-10 16:11 ` Tejun Heo
2017-02-15 8:45 ` Geert Uytterhoeven
2017-02-20 18:15 ` Bartlomiej Zolnierkiewicz
2017-02-21 22:18 ` Tejun Heo
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=20161230141249.GA4543@infradead.org \
--to=hch@infradead.org \
--cc=b.zolnierkie@samsung.com \
--cc=geert@linux-m68k.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=schmitzmic@gmail.com \
--cc=tj@kernel.org \
/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).