From: Randy Dunlap <rdunlap@infradead.org>
To: Mauro Carvalho Chehab <mchehab@kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Jens Axboe <axboe@kernel.dk>,
linux-kernel@vger.kernel.org, linux-m68k@lists.linux-m68k.org
Subject: Re: [PATCH 23/23] arch: m68k: q40: README: drop references to IDE driver
Date: Mon, 6 Jun 2022 09:07:51 -0700 [thread overview]
Message-ID: <d4de59db-62ba-22c3-3fc4-c69aa46b5c7a@infradead.org> (raw)
In-Reply-To: <39b24f99f5b71eb5ac025b438b7eb2a0df2258a1.1654529011.git.mchehab@kernel.org>
On 6/6/22 08:25, Mauro Carvalho Chehab wrote:
> Since IDE support was deleted by Christoph Hellwig <hch@lst.de>,
> Jun 16 2021, drop the left-over from README file.
>
> Fixes: b7fb14d3ac63 ("ide: remove the legacy ide driver")
> Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
>
> To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
> See [PATCH 00/23] at: https://lore.kernel.org/all/cover.1654529011.git.mchehab@kernel.org/
>
> arch/m68k/q40/README | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/arch/m68k/q40/README b/arch/m68k/q40/README
> index a4991d2d8af6..4db6db54d57a 100644
> --- a/arch/m68k/q40/README
> +++ b/arch/m68k/q40/README
> @@ -30,9 +30,7 @@ drivers used by the Q40, apart from the very obvious (console etc.):
> genrtc.c # RTC
> char/joystick/* # most of this should work, not
> # in default config.in
> - block/q40ide.c # startup for ide
> - ide* # see Documentation/ide/ide.rst
> - floppy.c # normal PC driver, DMA emu in asm/floppy.h
> + block/floppy.c # normal PC driver, DMA emu in asm/floppy.h
> # and arch/m68k/kernel/entry.S
> # see drivers/block/README.fd
> net/ne.c
--
~Randy
next prev parent reply other threads:[~2022-06-06 16:08 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 15:25 [PATCH 00/23] Update Documentation/ cross-references Mauro Carvalho Chehab
2022-06-06 15:25 ` [PATCH 01/23] dt-bindings: mfd: bd9571mwv: update rohm,bd9571mwv.yaml reference Mauro Carvalho Chehab
2022-06-07 19:25 ` Geert Uytterhoeven
2022-06-06 15:25 ` [PATCH 02/23] dt-bindings: interrupt-controller: update brcm,l2-intc.yaml reference Mauro Carvalho Chehab
2022-06-06 15:25 ` [PATCH 03/23] dt-bindings: arm: update vexpress-config.yaml references Mauro Carvalho Chehab
2022-06-06 15:44 ` Guenter Roeck
2022-06-06 15:25 ` [PATCH 04/23] dt-bindings: reset: update st,stih407-powerdown.yaml references Mauro Carvalho Chehab
2022-06-06 15:25 ` [PATCH 05/23] dt-bindings: mfd: rk808: update rockchip,rk808.yaml reference Mauro Carvalho Chehab
2022-06-06 15:25 ` [PATCH 06/23] dt-bindings: mmc: exynos-dw-mshc: update samsung,pinctrl.yaml reference Mauro Carvalho Chehab
2022-06-06 15:41 ` Krzysztof Kozlowski
2022-06-07 12:15 ` Krzysztof Kozlowski
2022-06-06 15:25 ` [PATCH 07/23] docs: netdev: update maintainer-netdev.rst reference Mauro Carvalho Chehab
2022-06-06 16:22 ` Jakub Kicinski
2022-06-06 15:25 ` [PATCH 08/23] docs: filesystems: update netfs-api.rst reference Mauro Carvalho Chehab
2022-06-06 15:25 ` [PATCH 09/23] Documentation: update watch_queue.rst references Mauro Carvalho Chehab
2022-06-06 15:56 ` Randy Dunlap
2022-06-06 15:25 ` [PATCH 10/23] Documentation: KVM: update s390-pv.rst reference Mauro Carvalho Chehab
2022-06-06 15:25 ` [PATCH 11/23] Documentation: KVM: update amd-memory-encryption.rst references Mauro Carvalho Chehab
2022-06-06 15:25 ` [PATCH 12/23] Documentation: KVM: update msr.rst reference Mauro Carvalho Chehab
2022-06-06 15:25 ` [PATCH 13/23] Documentation: KVM: update s390-diag.rst reference Mauro Carvalho Chehab
2022-06-06 15:25 ` [PATCH 14/23] MAINTAINERS: update arm,hdlcd.yaml reference Mauro Carvalho Chehab
2022-06-06 15:34 ` Andre Przywara
2022-06-06 17:13 ` Rob Herring
2022-06-06 15:25 ` [PATCH 15/23] MAINTAINERS: update arm,komeda.yaml reference Mauro Carvalho Chehab
2022-06-06 15:25 ` [PATCH 16/23] MAINTAINERS: update arm,malidp.yaml reference Mauro Carvalho Chehab
2022-06-06 15:25 ` [PATCH 17/23] MAINTAINERS: update cortina,gemini-ethernet.yaml reference Mauro Carvalho Chehab
2022-06-07 22:42 ` Linus Walleij
2022-06-06 15:25 ` [PATCH 18/23] MAINTAINERS: update dongwoon,dw9807-vcm.yaml reference Mauro Carvalho Chehab
2022-06-06 15:25 ` [PATCH 19/23] MAINTAINERS: update maxim,max77693.yaml reference Mauro Carvalho Chehab
2022-06-06 15:37 ` Krzysztof Kozlowski
2022-06-06 15:25 ` [PATCH 20/23] MAINTAINERS: update snps,axs10x-reset.yaml reference Mauro Carvalho Chehab
2022-06-06 15:25 ` [PATCH 21/23] objtool: update objtool.txt references Mauro Carvalho Chehab
2022-06-06 15:25 ` [PATCH 22/23] ASoC: wm8731: update wlf,wm8731.yaml reference Mauro Carvalho Chehab
2022-06-06 19:01 ` Rob Herring
2022-06-13 9:47 ` Charles Keepax
2022-06-06 15:25 ` [PATCH 23/23] arch: m68k: q40: README: drop references to IDE driver Mauro Carvalho Chehab
2022-06-06 16:07 ` Randy Dunlap [this message]
2022-06-07 8:07 ` Geert Uytterhoeven
2022-06-06 17:17 ` [PATCH 00/23] Update Documentation/ cross-references Rob Herring
2022-06-07 14:11 ` (subset) " Mark Brown
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=d4de59db-62ba-22c3-3fc4-c69aa46b5c7a@infradead.org \
--to=rdunlap@infradead.org \
--cc=axboe@kernel.dk \
--cc=corbet@lwn.net \
--cc=geert@linux-m68k.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=mchehab+huawei@kernel.org \
--cc=mchehab@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).