linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frieder Schrempf <frieder.schrempf@exceet.de>
To: ulf.hansson@linaro.org, hdegoede@redhat.com,
	quentin.schulz@free-electrons.com
Cc: gregkh@linuxfoundation.org, linus.walleij@linaro.org,
	shawn.lin@rock-chips.com, adrian.hunter@intel.com,
	baolin.wang@linaro.org, maxime.ripard@free-electrons.com,
	thomas.petazzoni@free-electrons.com,
	linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org,
	devel@driverdev.osuosl.org, icenowy@aosc.xyz, wens@csie.org
Subject: Re: [PATCH 2/2] mmc: Add mmc_force_detect_change_begin / _end functions
Date: Wed, 26 Sep 2018 16:44:44 +0200	[thread overview]
Message-ID: <f9028dcb-c217-4efc-60a7-d0a2c1804a08@exceet.de> (raw)
In-Reply-To: <CAPDyKFqDrdD+N+foLCwsVABtboz1Vn=OtJs14gp07zJfXHVKSA@mail.gmail.com>

Hi,

On Fri, Feb 09, 2018 at 03:01:00PM +0100, Ulf Hansson wrote:
> [...]
>
> >> > I'd like to know if any progress has been made on that problem 
(I may
> >> > have missed patches).
> >> > Had you had the time to look at the issue?
> >>
> >> I have looked at the issue, but not manage to cook some patches 
for it.
> >>
> >> However, it's on my top of my TODO list for mmc. No promises, but
> >> perhaps and hopefully I manage to get something posted during the
> >> coming release cycle.

I would be interested in a ESP8089 driver in mainline and that's why I 
want to pick up this discussion.

What is the current status of the "mmc_reprobe_device" implementation, 
that Hans was explaining and Ulf wanted to provide some months ago?

BTW, I am not on any of the mailing lists involved, so I tried to 
recreate the proper mail headers manually for the reply to the correct 
thread.

Thanks,
Frieder

> >>
> >
> > Cool! If you ever need some testing, I'd be glad to test your patches
> > (even if they are in a draft/RFC state).
> >
> > Also, when you send patches, I'd appreciate being Cc'ed so that I can
> > put my Tested-by :) Thanks!
>
> Absolutely! I appreciate it.

  parent reply	other threads:[~2018-09-26 14:44 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-21 14:35 [PATCH 0/2] add ESP8089 WiFi chip driver Quentin Schulz
2017-07-21 14:35 ` [PATCH 1/2] staging: net: wireless: add ESP8089 WiFi driver Quentin Schulz
2017-07-21 15:01   ` Greg KH
2017-07-21 16:47     ` Quentin Schulz
2017-07-21 16:52       ` Marcel Holtmann
2017-07-21 17:05         ` Quentin Schulz
2017-07-25  8:31           ` Kalle Valo
2017-07-21 15:01   ` Marcel Holtmann
2017-07-23  7:06   ` kbuild test robot
2017-07-23  8:25   ` kbuild test robot
2017-07-23  8:25   ` [PATCH] staging: net: wireless: fix badzero.cocci warnings kbuild test robot
2017-07-25 10:31   ` [PATCH 1/2] staging: net: wireless: add ESP8089 WiFi driver Dan Carpenter
2017-07-21 14:35 ` [PATCH 2/2] mmc: Add mmc_force_detect_change_begin / _end functions Quentin Schulz
2017-07-22 14:07   ` Shawn Lin
2017-08-30 12:44   ` Hans de Goede
2017-08-30 13:43     ` Ulf Hansson
2018-02-08 14:59       ` Quentin Schulz
2018-02-08 21:31         ` Ulf Hansson
2018-02-09  8:05           ` Quentin Schulz
2018-02-09 14:01             ` Ulf Hansson
2018-03-23  7:25               ` Quentin Schulz
2018-09-26 14:44               ` Frieder Schrempf [this message]
2018-09-26 20:19                 ` Hans de Goede
2018-09-27  8:14                   ` Maxime Ripard
2018-10-08  9:53                     ` Frieder Schrempf
2018-10-09  7:52                       ` Quentin Schulz
2018-10-09 14:03                         ` Frieder Schrempf

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=f9028dcb-c217-4efc-60a7-d0a2c1804a08@exceet.de \
    --to=frieder.schrempf@exceet.de \
    --cc=adrian.hunter@intel.com \
    --cc=baolin.wang@linaro.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hdegoede@redhat.com \
    --cc=icenowy@aosc.xyz \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=maxime.ripard@free-electrons.com \
    --cc=quentin.schulz@free-electrons.com \
    --cc=shawn.lin@rock-chips.com \
    --cc=thomas.petazzoni@free-electrons.com \
    --cc=ulf.hansson@linaro.org \
    --cc=wens@csie.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).