linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	linux-renesas-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org,
	linux-sh@vger.kernel.org
Subject: Re: [PATCH v2 0/6] mfd: tmio: simplify header and move to platform_data
Date: Tue, 9 Jul 2024 10:33:32 +0100	[thread overview]
Message-ID: <20240709093332.GD501857@google.com> (raw)
In-Reply-To: <CAMuHMdU6OquhF_WRxD+YxRfJwASepOb-pJp3wT7bvcpb1PHLDQ@mail.gmail.com>

On Sun, 07 Jul 2024, Geert Uytterhoeven wrote:

> On Sun, Jul 7, 2024 at 7:41 AM Wolfram Sang
> <wsa+renesas@sang-engineering.com> wrote:
> > On Fri, Feb 23, 2024 at 03:20:00PM +0000, Lee Jones wrote:
> > > On Tue, 13 Feb 2024 23:02:19 +0100, Wolfram Sang wrote:
> > > > Changes since v1:
> > > >
> > > > * rebased to rc4
> > > > * collected all needed acks (Thanks!)
> > > > * capitalized first letter in commit subject
> > > >
> > > > The MFD parts of the TMIO have been removed by Arnd, so that only the
> > > > SD/MMC related functionality is left. Remove the outdated remains in the
> > > > public header file and then move it to platform_data as the data is now
> > > > specific for the SD/MMC part.
> > > >
> > > > [...]
> > >
> > > Applied, thanks!
> > >
> > > [1/6] mfd: tmio: Remove obsolete platform_data
> > >       commit: 58d6d15662e4039fab7d786f0426843befa77ad4
> > > [2/6] mfd: tmio: Remove obsolete io accessors
> > >       commit: e927d7bac109d8ca1729dda47a8dbc220efdb50e
> > > [3/6] mmc: tmio/sdhi: Fix includes
> > >       commit: bed05c68aa8f078206143700cd37e42a0084155f
> > > [4/6] mfd: tmio: Update include files
> > >       commit: 3ef94c41db82573dc1e1dd6c259aec8ef6caaaf3
> > > [5/6] mfd: tmio: Sanitize comments
> > >       commit: 2d417dda59123b9523a19ce75fea3fd1056c3b4c
> > > [6/6] mfd: tmio: Move header to platform_data
> > >       commit: 858b29729c9d319b9cd1441646cc3af246d3c3f9
> >
> > This series is not upstream yet?
> 
> FTR, it entered linux-next in next-20240402, but disappeared after
> next-20240510.

That's very odd.  I cannot explain that.

I'll go apply it again.  Sorry for this.

-- 
Lee Jones [李琼斯]


  reply	other threads:[~2024-07-09  9:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13 22:02 [PATCH v2 0/6] mfd: tmio: simplify header and move to platform_data Wolfram Sang
2024-02-13 22:02 ` [PATCH v2 6/6] mfd: tmio: Move header " Wolfram Sang
2024-02-14 16:16   ` Geert Uytterhoeven
2024-02-23 15:20 ` [PATCH v2 0/6] mfd: tmio: simplify header and move " Lee Jones
2024-07-07  5:41   ` Wolfram Sang
2024-07-07 19:48     ` Geert Uytterhoeven
2024-07-09  9:33       ` Lee Jones [this message]
2024-07-09  9:40 ` Lee Jones
2024-07-09  9:41   ` Lee Jones
2024-07-09 10:37     ` Wolfram Sang

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=20240709093332.GD501857@google.com \
    --to=lee@kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-sh@vger.kernel.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).