linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: "Sasha Levin" <sashal@kernel.org>,
	devicetree <devicetree@vger.kernel.org>,
	linux-omap <linux-omap@vger.kernel.org>,
	stable <stable@vger.kernel.org>,
	"Benoît Cousson" <bcousson@baylibre.com>,
	kernel@pyra-handheld.com,
	"Discussions about the Letux Kernel"
	<letux-kernel@openphoenux.org>
Subject: Re: [PATCH 5/9] omap: pdata-quirks: remove openpandora quirks for mmc3 and wl1251
Date: Sat, 19 Oct 2019 09:22:55 -0700	[thread overview]
Message-ID: <20191019162255.GR5610@atomide.com> (raw)
In-Reply-To: <A0434659-A282-44AA-90E9-D234ADF8A04A@goldelico.com>

* H. Nikolaus Schaller <hns@goldelico.com> [191019 15:18]:
> 
> > Am 19.10.2019 um 15:36 schrieb Sasha Levin <sashal@kernel.org>:
> > 
> > Hi,
> > 
> > [This is an automated email]
> > 
> > This commit has been processed because it contains a "Fixes:" tag,
> > fixing commit: 81eef6ca92014 mmc: omap_hsmmc: Use dma_request_chan() for requesting DMA channel.
> > 
> > The bot has tested the following trees: v5.3.6, v4.19.79, v4.14.149, v4.9.196.
> > 
> > v5.3.6: Build OK!
> > v4.19.79: Failed to apply! Possible dependencies:
> >    Unable to calculate
> > 
> > v4.14.149: Failed to apply! Possible dependencies:
> >    0486738928bf0 ("ARM: OMAP1: ams-delta: add GPIO lookup tables")
> >    0920ca103f8d8 ("ARM: sa1100: provide infrastructure to support generic CF sockets")
> >    29786e9b6551b ("ARM: sa1100/assabet: convert to generic CF sockets")
> >    2bcb1be092370 ("Input: ams_delta_serio: Replace power GPIO with regulator")
> >    56de7570b3264 ("Input: ams_delta_serio: use private structure")
> >    7be893aa2d6a1 ("pcmcia: sa1100: provide generic CF support")
> >    b51af86559d4b ("ARM: sa1100/shannon: convert to generic CF sockets")
> >    b955153bfa68d ("ARM: sa1100/assabet: add BCR/BSR GPIO driver")
> >    c2f9b05fd5c12 ("media: arch: sh: ecovec: Use new renesas-ceu camera driver")
> >    df88c57689278 ("Input: ams_delta_serio: convert to platform driver")
> >    efdfeb079cc3b ("regulator: fixed: Convert to use GPIO descriptor only")
> 
> ^^^ this is the relevant one.
> 
> > 
> > v4.9.196: Failed to apply! Possible dependencies:
> >    0486738928bf0 ("ARM: OMAP1: ams-delta: add GPIO lookup tables")
> >    072f58af1dfbc ("ARM: dts: Add devicetree for the Raspberry Pi 3, for arm32 (v6)")
> >    1aa1d858f582c ("ARM: dts: bcm283x: Add dtsi for OTG mode")
> >    29786e9b6551b ("ARM: sa1100/assabet: convert to generic CF sockets")
> >    2bcb1be092370 ("Input: ams_delta_serio: Replace power GPIO with regulator")
> >    3bfe25fa9f8a5 ("ARM: dts: bcm283x: Move the BCM2837 DT contents from arm64 to arm.")
> >    56de7570b3264 ("Input: ams_delta_serio: use private structure")
> >    6c1b417adc8fa ("ARM: pxa: ezx: use the new pxa_camera platform_data")
> >    7ade445c26269 ("ARM: pxa: magician: Add support for ADS7846 touchscreen")
> >    8f9bafbb92c03 ("ARM: dts: aspeed: Add Romulus BMC platform")
> >    b24413180f560 ("License cleanup: add SPDX GPL-2.0 license identifier to files with no license")
> >    b5478c1b67bcd ("alpha: add asm/extable.h")
> >    b955153bfa68d ("ARM: sa1100/assabet: add BCR/BSR GPIO driver")
> >    d9fa04725f27f ("ARM: pxa: em-x270: use the new pxa_camera platform_data")
> >    df88c57689278 ("Input: ams_delta_serio: convert to platform driver")
> >    efdfeb079cc3b ("regulator: fixed: Convert to use GPIO descriptor only")
> >    fe7bf9dcfff5b ("ARM: dts: add a devicetree for Raidsonic NAS IB-4220-B")
> > 
> > 
> > NOTE: The patch will not be queued to stable trees until it is upstream.
> > 
> > How should we proceed with this patch?
> 
> I have checked and the reason is that 
> 
> efdfeb079cc3b ("regulator: fixed: Convert to use GPIO descriptor only")
> 
> was introduced after v.4.19 which was also partially reverted by this patch
> if based on mainline.
> 
> I have split it up into the partial revert of efdfeb079cc3b  for mainline
> and the real patch which now applies to all relevant stable trees.
> 
> So I'll sent a v2 asap.

Please also remove arch/arm/mach-omap2/hsmmc.[ch] as I think that
can be now done :)

Regards,

Tony

  parent reply	other threads:[~2019-10-19 16:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18 20:25 [PATCH 0/9] OpenPandora: make wl1251 connected to mmc3 sdio port of OpenPandora work again H. Nikolaus Schaller
2019-10-18 20:25 ` [PATCH 1/9] Documentation: dt: wireless: update wl1251 for sdio H. Nikolaus Schaller
2019-10-18 20:25 ` [PATCH 2/9] net: wireless: ti: wl1251 add device tree support H. Nikolaus Schaller
2019-10-18 20:25 ` [PATCH 3/9] DTS: ARM: pandora-common: define wl1251 as child node of mmc3 H. Nikolaus Schaller
2019-10-21 17:13   ` Tony Lindgren
2019-10-21 18:22     ` H. Nikolaus Schaller
2019-10-18 20:25 ` [PATCH 4/9] mmc: host: omap_hsmmc: add code for special init of wl1251 to get rid of pandora_wl1251_init_card H. Nikolaus Schaller
2019-10-18 20:25 ` [PATCH 5/9] omap: pdata-quirks: remove openpandora quirks for mmc3 and wl1251 H. Nikolaus Schaller
     [not found]   ` <20191019133621.C1CE421897@mail.kernel.org>
     [not found]     ` <A0434659-A282-44AA-90E9-D234ADF8A04A@goldelico.com>
2019-10-19 16:22       ` Tony Lindgren [this message]
2019-10-18 20:25 ` [PATCH 6/9] mmc: sdio: fix wl1251 vendor id H. Nikolaus Schaller
2019-10-18 20:25 ` [PATCH 7/9] mmc: core: fix wl1251 sdio quirks H. Nikolaus Schaller
2019-10-18 20:25 ` [PATCH 8/9] net: wireless: ti: wl1251 use new SDIO_VENDOR_ID_TI_WL1251 definition H. Nikolaus Schaller
2019-10-18 20:25 ` [PATCH 9/9] net: wireless: ti: remove local VENDOR_ID and DEVICE_ID definitions H. Nikolaus Schaller
2019-10-19 11:06 ` [PATCH 0/9] OpenPandora: make wl1251 connected to mmc3 sdio port of OpenPandora work again Kalle Valo
2019-10-19 11:25   ` H. Nikolaus Schaller
2019-10-19 11:34     ` Kalle Valo

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=20191019162255.GR5610@atomide.com \
    --to=tony@atomide.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hns@goldelico.com \
    --cc=kernel@pyra-handheld.com \
    --cc=letux-kernel@openphoenux.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.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).