From: Paul Mundt <lethal@linux-sh.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: saeed.bishara@gmail.com, linux-ide@vger.kernel.org,
saeed@marvell.com, htejun@gmail.com, liml@rtr.ca,
Saeed Bishara <saeed@il.marvell.com>
Subject: Re: [PATCH 2/2 v3] sata_mv: Support SoC controllers
Date: Sat, 2 Feb 2008 03:15:57 +0900 [thread overview]
Message-ID: <20080201181557.GA5999@linux-sh.org> (raw)
In-Reply-To: <47A34E8A.6020007@garzik.org>
On Fri, Feb 01, 2008 at 11:53:30AM -0500, Jeff Garzik wrote:
> saeed.bishara@gmail.com wrote:
> >--- /dev/null
> >+++ b/include/linux/sata_mv.h
> >@@ -0,0 +1,21 @@
> >+/*
> >+ * Marvell integrated SATA platfrom device data definition file.
> >+ *
> >+ * Saeed Bishara <saeed@marvell.com>
> >+ *
> >+ * This file is licensed under the terms of the GNU General Public
> >+ * License version 2. This program is licensed "as is" without any
> >+ * warranty of any kind, whether express or implied.
> >+ */
> >+
> >+#ifndef __LINUX_SATA_MV_H__
> >+#define __LINUX_SATA_MV_H__
> >+
> >+/*
> >+ * Sata private data
> >+ */
> >+struct mv_sata_platform_data {
> >+ int n_ports; /* number of sata ports */
> >+};
> >+
> >+#endif
>
> Overall, the patch is OK, but I fear adding way too many of these tiny
> includes, for each platform.
>
> Unless Paul M objects (pata_platform maintainer), I will rename
> linux/pata_platform.h to linux/ata_platform.h, and we can put your
> mv_sata_platform_data structure in there.
>
No objections from me, feel free to make the best use you can out of
what's there.
next prev parent reply other threads:[~2008-02-01 18:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 22:50 [PATCH 1/2 v3] sata_mv: Remove PCI dependency saeed.bishara
2008-01-30 22:50 ` [PATCH 2/2 v3] sata_mv: Support SoC controllers saeed.bishara
2008-02-01 16:53 ` Jeff Garzik
2008-02-01 18:15 ` Paul Mundt [this message]
2008-02-01 19:54 ` saeed bishara
2008-02-01 23:08 ` Jeff Garzik
2008-02-01 16:50 ` [PATCH 1/2 v3] sata_mv: Remove PCI dependency Jeff Garzik
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=20080201181557.GA5999@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=saeed.bishara@gmail.com \
--cc=saeed@il.marvell.com \
--cc=saeed@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.