linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jassisinghbrar@gmail.com (Jassi Brar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] pata_samsung: Add Samsung PATA controller driver
Date: Thu, 27 May 2010 18:18:42 +0900	[thread overview]
Message-ID: <AANLkTil--urA89NTNxpu6FrdmFbxSoJ82KdUhDC0OOpd@mail.gmail.com> (raw)
In-Reply-To: <20100527085714.GK4720@trinity.fluff.org>

On Thu, May 27, 2010 at 5:57 PM, Ben Dooks <ben-linux@fluff.org> wrote:
> On Thu, May 27, 2010 at 05:43:47PM +0900, Jassi Brar wrote:
>> On Thu, May 27, 2010 at 5:22 PM, Kukjin Kim <kgene.kim@samsung.com> wrote:
>> > From: Abhilash Kesavan <a.kesavan@samsung.com>
>> >
>> > Adds support for the Samsung PATA controller. This driver is based on the
>> > Libata subsystem and references the earlier patches sent for IDE subsystem.
>> >
>> > Signed-off-by: Abhilash Kesavan <a.kesavan@samsung.com>
>> > Signed-off-by: Kukjin Kim <kgene.kim@samsung.com>
>> > ---
>> > ?drivers/ata/Kconfig ? ? ? ?| ? ?9 +
>> > ?drivers/ata/Makefile ? ? ? | ? ?1 +
>> > ?drivers/ata/pata_samsung.c | ?591
>>
>> Fasten your seat belts before reading further....
>>
>> Rather than generic 'samsung', I would suggest the driver named
>> after the SoC, that is supported first(chronologically) in mainline kernel.
>> All newer SoCs should be simply taken to contain the controller of that SoC.
>> Otherwise, the same naming problem comes back to haunt us should
>> Samsung decides to use a different IP in future SoCs. What would we
>> call that driver? pata_samsung_v2.c ?
>
> I'm not so bothered, but it could be pata_samsung_cfcon or anything,
> a new block could be called pata_samsung_v2 or fred
well, then pata_samsung.c is better for we know chances of this IP change in
future SoCs are quite slim.
And even if it does change we shall call it
pata_samsung_really_final_this_time.c ;)

  reply	other threads:[~2010-05-27  9:18 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-27  8:22 [PATCH] Add Compact Flash driver for Samsung SoCs Kukjin Kim
2010-05-27  8:22 ` [PATCH 1/4] ARM: S3C64XX: Add support for Compact Flash driver on SMDK6410 Kukjin Kim
2010-05-27  8:52   ` Ben Dooks
2010-05-28  5:44     ` Marek Szyprowski
2010-06-02  2:31     ` Kukjin Kim
2010-05-27 19:45   ` Russell King - ARM Linux
2010-06-02  2:33     ` Kukjin Kim
2010-05-27  8:22 ` [PATCH 2/4] ARM: S5PV210: Add support for Compact Flash driver on SMDKV210/SMDKC110 Kukjin Kim
2010-05-27 19:46   ` Russell King - ARM Linux
2010-05-27  8:22 ` [PATCH 3/4] ARM: S5PC100: Add support for Compact Flash driver on SMDKC100 Kukjin Kim
2010-05-27 19:47   ` Russell King - ARM Linux
2010-06-02  2:34     ` Kukjin Kim
2010-05-27  8:22 ` [PATCH 4/4] pata_samsung: Add Samsung PATA controller driver Kukjin Kim
2010-05-27  8:43   ` Ben Dooks
2010-06-02  2:37     ` Kukjin Kim
2010-05-27  8:43   ` Jassi Brar
2010-05-27  8:57     ` Ben Dooks
2010-05-27  9:18       ` Jassi Brar [this message]
2010-05-27 10:17   ` Sergei Shtylyov
2010-06-02  2:42     ` Kukjin Kim
2010-06-02  9:51       ` Sergei Shtylyov
2010-06-03  0:25         ` Kukjin Kim
2010-05-27 21:52   ` Tejun Heo
2010-06-02  2:46     ` Kukjin Kim

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=AANLkTil--urA89NTNxpu6FrdmFbxSoJ82KdUhDC0OOpd@mail.gmail.com \
    --to=jassisinghbrar@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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).