From: Wolfram Sang <wsa@the-dreams.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux MMC List <linux-mmc@vger.kernel.org>,
linux-renesas-soc@vger.kernel.org,
Linux-sh list <linux-sh@vger.kernel.org>,
Simon Horman <horms@verge.net.au>,
Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>
Subject: Re: [PATCH 1/6] mmc: sh_mobile_sdhi: don't use array for DT configs
Date: Wed, 6 Apr 2016 12:27:26 +0200 [thread overview]
Message-ID: <20160406102726.GA1386@katana> (raw)
In-Reply-To: <CAMuHMdV=Ts_mF6MougLh1qqOTJV__x0Zu2TfMVsiPdfe+O--3g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 65 bytes --]
> It does remove 2 lines of source code ;-)
Memory on disk :)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@the-dreams.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux MMC List <linux-mmc@vger.kernel.org>,
linux-renesas-soc@vger.kernel.org,
Linux-sh list <linux-sh@vger.kernel.org>,
Simon Horman <horms@verge.net.au>,
Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>
Subject: Re: [PATCH 1/6] mmc: sh_mobile_sdhi: don't use array for DT configs
Date: Wed, 06 Apr 2016 10:27:26 +0000 [thread overview]
Message-ID: <20160406102726.GA1386@katana> (raw)
In-Reply-To: <CAMuHMdV=Ts_mF6MougLh1qqOTJV__x0Zu2TfMVsiPdfe+O--3g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 65 bytes --]
> It does remove 2 lines of source code ;-)
Memory on disk :)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-04-06 10:27 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 9:25 [PATCH 0/6] mmc: tmio/sdhi: clean up cruft Wolfram Sang
2016-04-06 9:25 ` Wolfram Sang
2016-04-06 9:25 ` [PATCH 1/6] mmc: sh_mobile_sdhi: don't use array for DT configs Wolfram Sang
2016-04-06 9:25 ` Wolfram Sang
2016-04-06 9:56 ` Geert Uytterhoeven
2016-04-06 9:56 ` Geert Uytterhoeven
2016-04-06 10:27 ` Wolfram Sang [this message]
2016-04-06 10:27 ` Wolfram Sang
2016-04-06 9:25 ` [PATCH 2/6] mmc: sh_mobile_sdhi: remove obsolete irq_by_name registration Wolfram Sang
2016-04-06 9:25 ` Wolfram Sang
2016-04-18 8:21 ` Ulf Hansson
2016-04-18 8:21 ` Ulf Hansson
2016-04-19 9:37 ` Wolfram Sang
2016-04-19 9:37 ` Wolfram Sang
2016-04-27 22:54 ` Rich Felker
2016-04-27 22:54 ` Rich Felker
2016-04-28 3:59 ` Yoshinori Sato
2016-04-28 3:59 ` Yoshinori Sato
2016-04-28 6:19 ` Wolfram Sang
2016-04-28 6:19 ` Wolfram Sang
2016-04-28 8:03 ` Geert Uytterhoeven
2016-04-28 8:03 ` Geert Uytterhoeven
2016-04-26 15:47 ` Wolfram Sang
2016-04-26 15:47 ` Wolfram Sang
2016-04-06 9:25 ` [PATCH 3/6] mmc: tmio: remove now unneeded seperate irq handlers Wolfram Sang
2016-04-06 9:25 ` Wolfram Sang
2016-04-06 9:25 ` [PATCH 4/6] mmc: tmio: simplify irq handler Wolfram Sang
2016-04-06 9:25 ` Wolfram Sang
2016-04-06 9:25 ` [PATCH 5/6] mmc: tmio: merge distributed include files Wolfram Sang
2016-04-06 9:25 ` Wolfram Sang
2016-04-06 9:34 ` [PATCH v2 " Wolfram Sang
2016-04-06 9:34 ` Wolfram Sang
2016-04-06 9:25 ` [PATCH 6/6] mmc: sh_mobile_sdhi: simplify code for voltage switching Wolfram Sang
2016-04-06 9:25 ` 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=20160406102726.GA1386@katana \
--to=wsa@the-dreams.de \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@gmail.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-sh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.