linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Christopher Heiny <cheiny@synaptics.com>
Cc: Linux Input <linux-input@vger.kernel.org>,
	Andrew Duggan <aduggan@synaptics.com>,
	Vincent Huang <vincent.huang@tw.synaptics.com>,
	Vivian Ly <vly@synaptics.com>,
	Daniel Rosenberg <daniel.rosenberg@synaptics.com>,
	Jean Delvare <khali@linux-fr.org>,
	Joerie de Gram <j.de.gram@gmail.com>,
	Linus Walleij <linus.walleij@stericsson.com>,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>
Subject: Re: [PATCH] input synaptics-rmi4: Transport layer renaming.
Date: Thu, 26 Dec 2013 15:43:55 -0800	[thread overview]
Message-ID: <20131226234355.GH18562@core.coreip.homeip.net> (raw)
In-Reply-To: <1387315890-21681-1-git-send-email-cheiny@synaptics.com>

On Tue, Dec 17, 2013 at 01:31:30PM -0800, Christopher Heiny wrote:
> The current RMI4 driver uses the term "physical" for two different logical
> entities: the communications transport layer (I2C, SPI, and so on), and the
> actual RMI4 device that is being communicated with.  Such usage makes the
> code harder to understand due to confusion as to just which elements are
> being referred to.
> 
> This patch renames the transport layer elements in order to eliminate this
> confusion.  Much of the renaming was accomplished by the following Bash script
> 
>   #!/bin/bash
>   #
>   # Update RMI4 driver transport layer naming.
>   #
> 
>   files="rmi_bus.c rmi_bus.h rmi_driver.c rmi_driver.h rmi_f01.c rmi_i2c.c"
>   cd drivers/input/rmi4
> 
>   for f in $files ; do
>     echo $f
>     sed -i.bak s/rmi_phys_device/rmi_transport_dev/g $f
>     sed -i.bak s/rmi_phys_info/rmi_transport_info/g $f
>     sed -i.bak "s/rmi_transport_dev \*phys/rmi_transport_dev \*xport/g" $f
>     sed -i.bak "s/rmi_transport_dev \*rmi_phys/rmi_transport_dev \*xport/g" $f
>     sed -i.bak "s/phys\([^i]\)/xport\1/g" $f
>     sed -i.bak "s/->phys/->xport/g" $f
>     sed -i.bak "s/register_physical_device/register_transport_device/g" $f
>     sed -i.bak "s/physical_device_count/transport_device_count/g" $f
>   done
> 
> although some changes proved easier to simply do by hand, particularly in the
> comments.  Changes are confined strictly to the renaming, to keep the patch
> relatively simple.
> 
> Signed-off-by: Christopher Heiny <cheiny@synaptics.com>
> Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>


Applied, thank you.

-- 
Dmitry

      reply	other threads:[~2013-12-26 23:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-17 21:31 [PATCH] input synaptics-rmi4: Transport layer renaming Christopher Heiny
2013-12-26 23:43 ` Dmitry Torokhov [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=20131226234355.GH18562@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=aduggan@synaptics.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=cheiny@synaptics.com \
    --cc=daniel.rosenberg@synaptics.com \
    --cc=j.de.gram@gmail.com \
    --cc=khali@linux-fr.org \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-input@vger.kernel.org \
    --cc=vincent.huang@tw.synaptics.com \
    --cc=vly@synaptics.com \
    /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).