linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marek Vasut <marex-ynQEQJNshbs@public.gmane.org>
To: "Uwe Kleine-König"
	<u.kleine-koenig-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Cc: Wolfram Sang <wolfram-z923LK4zBo2bacvFa/9K2g@public.gmane.org>,
	linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Lucas Stach <l.stach-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Subject: Re: I2C_M_RECV_LEN for i2c-mxs
Date: Sun, 14 Apr 2013 19:54:38 +0200	[thread overview]
Message-ID: <201304141954.38902.marex@denx.de> (raw)
In-Reply-To: <20130412093003.GE30416-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>

Hi Uwe,

CCing Lucas Stach too, are you two not in the same office now ? ;-)

> Hello,
> 
> I'm currently trying to teach the i2c-mxs driver to handle the
> I2C_M_RECV_LEN flag but failed up to now. Maybe someone has an good idea
> how to make it running?
> 
> My current patch looks as follows:

Try basing your patch on top of Lucas's, they looked very reasonable. I think WS 
should have applied them by now. Wolfram, what's the status of those three mxs-
i2c patches from Lucas, can you tell?

Best regards,
Marek Vasut

      parent reply	other threads:[~2013-04-14 17:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-12  9:30 I2C_M_RECV_LEN for i2c-mxs Uwe Kleine-König
     [not found] ` <20130412093003.GE30416-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2013-04-12 15:37   ` Wolfram Sang
     [not found]     ` <20130412153757.GA10241-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
2013-04-12 18:26       ` Uwe Kleine-König
     [not found]         ` <20130412182611.GG30416-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2013-04-14 11:57           ` Wolfram Sang
     [not found]             ` <20130414115757.GA9013-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
2013-04-16  7:59               ` Uwe Kleine-König
2013-04-14 17:54   ` Marek Vasut [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=201304141954.38902.marex@denx.de \
    --to=marex-ynqeqjnshbs@public.gmane.org \
    --cc=l.stach-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=u.kleine-koenig-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
    --cc=wolfram-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).