devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kernel@stlinux.com,
	devicetree@vger.kernel.org
Subject: Re: [PATCH 1/1] i2c: i2c-st: Rename clock reference to something that exists
Date: Thu, 22 Jan 2015 14:54:40 +0000	[thread overview]
Message-ID: <20150122145440.GD9129@x1> (raw)
In-Reply-To: <20150122141427.GA3413@katana>

On Thu, 22 Jan 2015, Wolfram Sang wrote:

> On Thu, Jan 22, 2015 at 12:18:19PM +0000, Lee Jones wrote:
> > Wolfram,
> > 
> > This patch has been on the list since forever.
> 
> For reasons :)
> 
> a) It was not CCed to the i2c list, so it doesn't show up in patchwork
> which does the patch tracking for me.
> 
> b) I was always under the impression that Maxime is going to take it?
> He said so.
> 
> > I have Acks from the driver author, so I'm going to take this through
> > the MFD tree.  If you perk up later and decide to take it though the
> > I2C tree instead, let me know and I'll remove it from MFD.
> 
> Well, I2C makes more sense than MFD, so I'll pick it up right now.
> ST-tree would have also been fine.

Works for me.  Thanks dude.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

      reply	other threads:[~2015-01-22 14:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-28 14:02 [PATCH 1/1] i2c: i2c-st: Rename clock reference to something that exists Lee Jones
     [not found] ` <1409234523-20240-1-git-send-email-lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2014-08-28 14:31   ` [STLinux Kernel] " Maxime Coquelin
2015-01-21 15:26     ` Lee Jones
2015-01-22  9:34   ` Peter Griffin
2015-01-22 14:18   ` Wolfram Sang
2015-01-22 12:18 ` Lee Jones
2015-01-22 14:14   ` Wolfram Sang
2015-01-22 14:54     ` Lee Jones [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=20150122145440.GD9129@x1 \
    --to=lee.jones@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@stlinux.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wsa@the-dreams.de \
    /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).