linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Jarkko Nikula <jarkko.nikula@bitmer.com>
Cc: Chris Ball <cjb@laptop.org>,
	linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
	linux-mmc@vger.kernel.org, Jarkko Lavinen <j.lavinen@samsung.com>
Subject: Re: [PATCH 2/8] mmc: omap: Fix DMA configuration to not rely on device id
Date: Fri, 29 Nov 2013 09:13:55 -0800	[thread overview]
Message-ID: <20131129171354.GO31534@atomide.com> (raw)
In-Reply-To: <52976BA4.1000700@bitmer.com>

* Jarkko Nikula <jarkko.nikula@bitmer.com> [131128 08:14]:
> Hi
> 
> On 11/27/2013 11:59 PM, Tony Lindgren wrote:
> > * Chris Ball <cjb@laptop.org> [131127 13:48]:
> >> Hi,
> >>
> >> On Wed, Nov 27 2013, Jarkko Nikula wrote:
> >>> Can you enlighten me what's the proper way to get patches to mmc since
> >>> I cannot figure out working methodology from MAINTAINERS file?
> >>
> >> Sorry about this, Jarkko.
> >>
> >> Since I don't have omap.c hardware, I'm generally going to wait for
> >> a Tested-by/Acked-by from someone else on patches like these.  We
> >> actually have a maintainer already listed for the driver, Jarkko
> >> Lavinen <jarkko.lavinen@nokia.com>.
> >>
> >> So, maybe the MAINTAINERS section for drivers/mmc/host/omap.c needs
> >> an update?  Feel free to send me patches to it.  Either way, I'll
> >> start treating Aaro and Jarkko (Nikula) as maintainers for this
> >> driver.
> > 
> Oh, I see. I even didn't check ./scripts/get_maintainer.pl nor check
> MAINTAINERS file further than main MMC entry as I knew Jarkko L. is not
> working anymore for Nokia. Sorry, we should have noticed that.
> 
> > Hmm looks like here's a reasonably recent update that we've missed
> > from Jarkko Lavinen to update his email address:
> > 
> > http://lkml.org/lkml/2013/10/4/142
> > 
> > I've updated Jarkko Lavinen's address in this mail, we should
> > probably also patch the MAINTAINERS file for that, and then see if
> > Aaro and Jarkko Nikula are interested to be listed there as well.
> > 
> I can volunteer. Not that I know much about mmc but I like to keep my
> legacy hw still running :-)

Sounds good to me, good to hear :)

Regards,

Tony

  reply	other threads:[~2013-11-29 17:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1384396537-3486-1-git-send-email-tony@atomide.com>
2013-11-14  2:35 ` [PATCH 2/8] mmc: omap: Fix DMA configuration to not rely on device id Tony Lindgren
2013-11-18 18:47   ` Tony Lindgren
2013-11-26 23:33     ` Chris Ball
2013-11-26 23:52       ` Tony Lindgren
2013-11-27 20:57       ` Jarkko Nikula
2013-11-27 21:37         ` Tony Lindgren
2013-11-28 17:02           ` Jarkko Nikula
2013-11-29 16:34             ` Tony Lindgren
2013-11-27 21:47         ` Chris Ball
2013-11-27 21:59           ` Tony Lindgren
2013-11-28 16:13             ` Jarkko Nikula
2013-11-29 17:13               ` Tony Lindgren [this message]
2013-11-30  0:38   ` Joel Fernandes
2013-11-30 17:33     ` Tony Lindgren
2013-11-14  2:35 ` [PATCH 3/8] mmc: omap: Fix I2C dependency and make driver usable with device tree Tony Lindgren
2013-11-14 11:05   ` Mark Rutland
2013-11-14 17:25     ` Tony Lindgren
2013-11-26 23:34       ` Chris Ball

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=20131129171354.GO31534@atomide.com \
    --to=tony@atomide.com \
    --cc=cjb@laptop.org \
    --cc=j.lavinen@samsung.com \
    --cc=jarkko.nikula@bitmer.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-omap@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).