From: Wolfram Sang <wsa@the-dreams.de>
To: Doug Anderson <dianders@chromium.org>
Cc: Lee Jones <lee.jones@linaro.org>, Dave Jones <davej@redhat.com>,
rspangler@chromium.org, sjg@chromium.org, sameo@linux.intel.com,
wfrichar@chromium.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: cros_ec: Remove EC_I2C_FLAG_10BIT
Date: Fri, 27 Jun 2014 14:34:43 +0200 [thread overview]
Message-ID: <20140627123443.GC29156@katana> (raw)
In-Reply-To: <1403558406-14519-1-git-send-email-dianders@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]
On Mon, Jun 23, 2014 at 02:20:06PM -0700, Doug Anderson wrote:
> In <https://lkml.org/lkml/2014/6/10/265> pointed out that the 10-bit
> flag in the cros_ec_tunnel was useless. It went into a 16-bit flags
> field but was defined at (1 << 16).
>
> Since we have no 10-bit i2c devices on the other side of the tunnel on
> any known devices this was never a problem. Until we do it makes
> sense to remove this code. On the EC side the code to handle this
> flag was removed in <https://chromium-review.googlesource.com/204162>.
>
> Reported-by: Dave Jones <davej@redhat.com>
> Signed-off-by: Doug Anderson <dianders@chromium.org>
> ---
> Note that this patch is based atop my current series of posts to
> cleanup cros_ec. It wouldn't be hard to apply it to the current ToT
> if someone wants to land this before the others.
I could take it into my tree, but I think it makes more sense if we
simply append it to your cleanup series?
Reviewed-by: Wolfram Sang <wsa@the-dreams.de>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-06-27 12:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 21:20 [PATCH] i2c: cros_ec: Remove EC_I2C_FLAG_10BIT Doug Anderson
[not found] ` <1403558406-14519-1-git-send-email-dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2014-06-24 8:59 ` Lee Jones
2014-09-30 6:07 ` Wolfram Sang
2014-06-24 15:53 ` Simon Glass
2014-06-27 12:34 ` Wolfram Sang [this message]
2014-06-27 15:49 ` Doug Anderson
[not found] ` <CAD=FV=WLw2D3sw2LaWt0SJXNEFSBk08eKOCa9O_zt=58UN+MLA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-27 15:59 ` 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=20140627123443.GC29156@katana \
--to=wsa@the-dreams.de \
--cc=davej@redhat.com \
--cc=dianders@chromium.org \
--cc=lee.jones@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rspangler@chromium.org \
--cc=sameo@linux.intel.com \
--cc=sjg@chromium.org \
--cc=wfrichar@chromium.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).