From: Fabio Estevam <festevam-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
Cc: Fabio Estevam
<fabio.estevam-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 03/13] i2c: i2c-mxs: Let device core handle pinctrl
Date: Sat, 8 Jun 2013 04:49:08 -0300 [thread overview]
Message-ID: <CAOMZO5DQW7fB3Xi8mvymWhVZYcjuwTHKPyfDsWZCfw79AdUT7g@mail.gmail.com> (raw)
In-Reply-To: <20130608071521.GA3052@katana>
On Sat, Jun 8, 2013 at 4:15 AM, Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org> wrote:
> Yes, with series like this, you really need a cover-letter and CC it to
> all people involved. And mention there if you want these patches go via
> a specific tree or each patch via the corresponding subsystem tree. And
> mention if the patches are depending on each other. Otherwise I don't
> really know what to do with these patches.
Ok, understood, Wolfram.
Please apply in your tree, if it looks good for you.
Thanks,
Fabio Estevam
next prev parent reply other threads:[~2013-06-08 7:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1367863561-11534-1-git-send-email-fabio.estevam@freescale.com>
[not found] ` <1367863561-11534-1-git-send-email-fabio.estevam-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2013-05-06 18:05 ` [PATCH 02/13] i2c: i2c-imx: Let device core handle pinctrl Fabio Estevam
2013-05-06 18:05 ` [PATCH 03/13] i2c: i2c-mxs: " Fabio Estevam
[not found] ` <1367863561-11534-3-git-send-email-fabio.estevam-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2013-05-26 20:58 ` Fabio Estevam
[not found] ` <CAOMZO5Bju3v4gXayzZ6vMjr9WrSqcYWN+6fnyKMc3AaoYt44Gg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-08 7:15 ` Wolfram Sang
2013-06-08 7:49 ` Fabio Estevam [this message]
[not found] ` <CAOMZO5DQW7fB3Xi8mvymWhVZYcjuwTHKPyfDsWZCfw79AdUT7g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-10 13:51 ` 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=CAOMZO5DQW7fB3Xi8mvymWhVZYcjuwTHKPyfDsWZCfw79AdUT7g@mail.gmail.com \
--to=festevam-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=fabio.estevam-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.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).