public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Karol Lewandowski <k.lewandowsk@samsung.com>
Cc: w.sang@pengutronix.de, ben-linux@fluff.org,
	m.szyprowski@samsung.com, thomas.abraham@linaro.org,
	linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
	devicetree-discuss@lists.ozlabs.org,
	linux-samsung-soc@vger.kernel.org, t.stanislaws@samsung.com,
	kyungmin.park@samsung.com
Subject: Re: [PATCH 2/3] i2c-s3c2410: Rework device type handling
Date: Wed, 21 Mar 2012 20:30:32 +0000	[thread overview]
Message-ID: <20120321203032.GQ3226@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1332357113-2973-3-git-send-email-k.lewandowsk@samsung.com>

[-- Attachment #1: Type: text/plain, Size: 436 bytes --]

On Wed, Mar 21, 2012 at 08:11:52PM +0100, Karol Lewandowski wrote:
> Reorganize driver a bit to better handle device tree-based systems:
> 
>  - move machine type to driver's private structure instead of
>    quering platform device variants in runtime
> 
>  - replace s3c24xx_i2c_type enum with unsigned int that holds
>    bitmask with revision-specific quirks

Reviewed-by: Mark Brown <broonie@opensource.wolfsonmicro.com>

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-03-21 20:30 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-21 19:11 [PATCH v3 0/3] i2c-s3c2410: Updates for exynos4210 and DT-based systems Karol Lewandowski
2012-03-21 19:11 ` [PATCH 1/3] i2c-s3c2410: Drop unused define Karol Lewandowski
2012-04-18 10:56   ` Wolfram Sang
2012-03-21 19:11 ` [PATCH 2/3] i2c-s3c2410: Rework device type handling Karol Lewandowski
2012-03-21 20:30   ` Mark Brown [this message]
2012-04-17 17:31   ` Wolfram Sang
2012-04-18 11:55     ` Karol Lewandowski
2012-04-18 13:39       ` Wolfram Sang
2012-03-21 19:11 ` [PATCH 3/3] i2c-s3c2410: Add HDMIPHY quirk for S3C2440 Karol Lewandowski
2012-04-17 17:40   ` Wolfram Sang
2012-04-18 12:11     ` Marek Szyprowski
2012-04-18 13:46       ` Wolfram Sang
2012-04-18 16:31         ` Karol Lewandowski
2012-04-23 10:01           ` Wolfram Sang
2012-04-23 16:22             ` Karol Lewandowski
2012-04-13  9:30 ` [PATCH v3 0/3] i2c-s3c2410: Updates for exynos4210 and DT-based systems Karol Lewandowski
  -- strict thread matches above, loose matches on Subject: below --
2012-03-13 16:54 [PATCH 0/3 v2] " Karol Lewandowski
2012-03-13 16:54 ` [PATCH 2/3] i2c-s3c2410: Rework device type handling Karol Lewandowski
2012-03-14 17:29   ` Mark Brown
2012-03-15 10:04     ` Karol Lewandowski
2012-03-15 12:56       ` Mark Brown
2012-03-15 16:54         ` Karol Lewandowski
2012-03-19 19:55           ` Mark Brown
2012-03-21 10:33             ` Karol Lewandowski
2012-03-21 11:50               ` Mark Brown
2012-03-21 11:54                 ` Karol Lewandowski

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=20120321203032.GQ3226@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=ben-linux@fluff.org \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=k.lewandowsk@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=t.stanislaws@samsung.com \
    --cc=thomas.abraham@linaro.org \
    --cc=w.sang@pengutronix.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