linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] mmc: omap: Remove Unused Code
Date: Mon, 17 Jul 2017 00:17:28 -0700	[thread overview]
Message-ID: <20170717071727.GF10026@atomide.com> (raw)
In-Reply-To: <CAPDyKFqk1fnL_CFSfgg2P44-KD9H=6mvK6ppXoDe=Xy38ujiFA@mail.gmail.com>

* Ulf Hansson <ulf.hansson@linaro.org> [170717 00:09]:
> On 17 July 2017 at 08:01, Tony Lindgren <tony@atomide.com> wrote:
> > * Faiz Abbas <faiz_abbas@ti.com> [170714 05:48]:
> >> This patch series removes some code in omap_hsmmc.c
> >> and hsmmc.c and members from hsmmc.h and
> >> hsmmc-omap.h which are not used anymore post
> >> conversion to device-tree.
> >
> > Hey that's nice! That gets us a bit closer removing the
> > old platform data for that driver.
> 
> Tony,
> 
> As it seems Kishon is working on some more omap_hsmmc changes, I
> wondering whether it's fine if I pick this series via my mmc tree. To
> avoid merge conflicts later on?

Yes please do and for both feel free to add:

Acked-by: Tony Lindgren <tony@atomide.com>

And if you want to be extra nice, please add these two directly
on v4.13-rc1 before merging them into your branch in case I need
to merge them in too for any unlikely SoC related conflicts.

Regards,

Tony

      reply	other threads:[~2017-07-17  7:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-14 12:46 [PATCH 0/2] mmc: omap: Remove Unused Code Faiz Abbas
2017-07-14 12:46 ` [PATCH 1/2] ARM: OMAP2+: hsmmc.c: Remove dead code Faiz Abbas
2017-07-17 13:08   ` Ulf Hansson
2017-07-18 10:19     ` Faiz Abbas
2017-07-14 12:46 ` [PATCH 2/2] mmc: host: omap_hsmmc: remove unused platform callbacks Faiz Abbas
2017-07-17  6:01 ` [PATCH 0/2] mmc: omap: Remove Unused Code Tony Lindgren
2017-07-17  7:09   ` Ulf Hansson
2017-07-17  7:17     ` Tony Lindgren [this message]

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=20170717071727.GF10026@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.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).