linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Lee Jones <lee@kernel.org>, Ulf Hansson <ulf.hansson@linaro.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: linux-next: manual merge of the mfd tree with the mmc tree
Date: Wed, 10 Jul 2024 14:10:10 +1000	[thread overview]
Message-ID: <20240710141010.4fbd65a0@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1780 bytes --]

Hi all,

Today's linux-next merge of the mfd tree got a conflict in:

  include/linux/mfd/tmio.h

between commits:

  89f415b99050 ("mfd: tmio: Remove obsolete .set_clk_div() callback")
  f86937afb446 ("mmc: tmio: Remove obsolete .set_pwr() callback()")

from the mmc tree and commit:

  70b46487b155 ("mfd: tmio: Move header to platform_data")

from the mfd tree.

I fixed it up (I removed the file and applied the following patch) and
can carry the fix as necessary. This is now fixed as far as linux-next
is concerned, but any non trivial conflicts should be mentioned to your
upstream maintainer when your tree is submitted for merging.  You may
also want to consider cooperating with the maintainer of the conflicting
tree to minimise any particularly complex conflicts.

From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Wed, 10 Jul 2024 14:06:29 +1000
Subject: [PATCH] fixup for "mfd: tmio: Move header to platform_data"

interacting with "mfd: tmio: Remove obsolete .set_clk_div() callback"
and "mmc: tmio: Remove obsolete .set_pwr() callback()" from the mmc tree

Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
 include/linux/platform_data/tmio.h | 2 --
 1 file changed, 2 deletions(-)

diff --git a/include/linux/platform_data/tmio.h b/include/linux/platform_data/tmio.h
index 1cf418643da9..b060124ba1ae 100644
--- a/include/linux/platform_data/tmio.h
+++ b/include/linux/platform_data/tmio.h
@@ -58,7 +58,5 @@ struct tmio_mmc_data {
 	dma_addr_t			dma_rx_offset;
 	unsigned int			max_blk_count;
 	unsigned short			max_segs;
-	void (*set_pwr)(struct platform_device *host, int state);
-	void (*set_clk_div)(struct platform_device *host, int state);
 };
 #endif
-- 
2.43.0

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2024-07-10  4:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-10  4:10 Stephen Rothwell [this message]
2024-07-10  6:21 ` linux-next: manual merge of the mfd tree with the mmc tree Wolfram Sang
  -- strict thread matches above, loose matches on Subject: below --
2012-12-07  3:24 Stephen Rothwell

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=20240710141010.4fbd65a0@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=geert+renesas@glider.be \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=ulf.hansson@linaro.org \
    --cc=wsa+renesas@sang-engineering.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).