linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jaehoon Chung <jh80.chung@samsung.com>
To: linux-pci@vger.kernel.org
Cc: helgaas@google.com, krzk@kernel.org,
	linux-kernel@vger.kernel.org, jingoohan1@gmail.com,
	javier@osg.samsung.com, kgene@kernel.org,
	linux-samsung-soc@vger.kernel.org, cpgs@samsung.com,
	Jaehoon Chung <jh80.chung@samsung.com>
Subject: [PATCH 0/4] PCI: exynos: cleans the minor things
Date: Mon, 19 Dec 2016 17:17:36 +0900	[thread overview]
Message-ID: <20161219081740.5457-1-jh80.chung@samsung.com> (raw)

Current pci-exnoys.c is used for only EXYNOS5440.
Even if there is no use-case, just cleans the codes for maintaining.

In future, I will upstream for Exynso5433(TM2).
Before sending patches for exynos5433, i want to reuse the some codse in pic-exynos.c.
This patch is for perparing it.

My Final goal is to apply the pcie-exynos5433 into v4.11.

Jaehoon Chung (4):
  PCI: exynos: replace to one register accessor from each accessors
  PCI: exynos: Remove the unnecessary variables
  PCI: exynos: Use the bitops API to operate the bit shifting
  PCI: exynos: remove the duplicated codes

 drivers/pci/host/pci-exynos.c | 260 +++++++++++++++++++-----------------------
 1 file changed, 116 insertions(+), 144 deletions(-)

-- 
2.10.2

             reply	other threads:[~2016-12-19  8:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-19  8:17 Jaehoon Chung [this message]
2016-12-19  8:17 ` [PATCH 1/4] PCI: exynos: replace to one register accessor from each accessors Jaehoon Chung
     [not found]   ` <CGME20161221061214epcas3p3033a93bbda1c9f4247a676750a10cdb1@epcas3p3.samsung.com>
2016-12-21  6:14     ` [1/4] " pankaj.dubey
2016-12-24  9:27   ` [PATCH 1/4] " Krzysztof Kozlowski
2016-12-19  8:17 ` [PATCH 2/4] PCI: exynos: Remove the unnecessary variables Jaehoon Chung
     [not found]   ` <CGME20161221061724epcas4p1020ae6823df0660fba63435130144a33@epcas4p1.samsung.com>
2016-12-21  6:19     ` [2/4] " pankaj.dubey
2016-12-24 10:52   ` [PATCH 2/4] " Krzysztof Kozlowski
2016-12-19  8:17 ` [PATCH 3/4] PCI: exynos: Use the bitops API to operate the bit shifting Jaehoon Chung
     [not found]   ` <CGME20161221061953epcas1p433e2197077f1c9e1a46587d7aa602b2f@epcas1p4.samsung.com>
2016-12-21  6:22     ` [3/4] " pankaj.dubey
2016-12-24 10:54   ` [PATCH 3/4] " Krzysztof Kozlowski
2016-12-19  8:17 ` [PATCH 4/4] PCI: exynos: remove the duplicated codes Jaehoon Chung
     [not found]   ` <CGME20161221062054epcas1p178b0503e66acc9d005a6e08fa8753954@epcas1p1.samsung.com>
2016-12-21  6:23     ` [4/4] " pankaj.dubey
2016-12-24 11:02   ` [PATCH 4/4] " Krzysztof Kozlowski
  -- strict thread matches above, loose matches on Subject: below --
2016-12-19  8:16 [PATCH 0/4] PCI: exynos: cleans the minor things Jaehoon Chung
2016-12-20 17:35 ` Bartlomiej Zolnierkiewicz
2016-12-26 13:52   ` Jingoo Han

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=20161219081740.5457-1-jh80.chung@samsung.com \
    --to=jh80.chung@samsung.com \
    --cc=cpgs@samsung.com \
    --cc=helgaas@google.com \
    --cc=javier@osg.samsung.com \
    --cc=jingoohan1@gmail.com \
    --cc=kgene@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.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).