ahci: add an observed PCI ID for Marvell 88se9172 SATA controller

Applied to libata/for-3.10-fixes.  In the future, please base patches
on top of git://git.kernel.org/pub/scm/linux/kernel/git/tj/libata.git
for-XXX branches.

Thanks.

From fcce9a35f8faaa1f52236c554ef1b15d99a7537e Mon Sep 17 00:00:00 2001
From: George Spelvin <linux@horizon.com>
Date: Wed, 29 May 2013 10:20:35 +0900

A third possible PCI ID, as personally observed, and found in the
pci.ids list.

Signed-off-by: George Spelvin <linux@horizon.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
---
 drivers/ata/ahci.c | 2 ++
 1 file changed, 2 insertions(+)

> Applied to libata/for-3.10-fixes.  In the future, please base patches
> on top of git://git.kernel.org/pub/scm/linux/kernel/git/tj/libata.git
> for-XXX branches.

As you saw, it didn't initially occur to me to prepare a patch at all;
it seemed such a trivial copy/paste/one-character-edit exercise.
After diagnosis, the most difficult part was writing a meaningful
commit message.

Which I presumed would be easier for you; a lot of the difficulty for me
was trying to figure out one line that would fit the ongoing narrative
that is the kernel changelog.

I was actually surprised when you asked for a full patch, so I just sent
you a copy of my private commit, with an improved commit message and S-o-b.
(Should I have added "Cc: stable" to it?)

But since I now know you prefer even trivial changes like this in formal
patch form, I'll try to do it right in future.
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Hello,

On Wed, May 29, 2013 at 08:36:27AM -0400, George Spelvin wrote:
> As you saw, it didn't initially occur to me to prepare a patch at all;
> it seemed such a trivial copy/paste/one-character-edit exercise.
> After diagnosis, the most difficult part was writing a meaningful
> commit message.
> 
> Which I presumed would be easier for you; a lot of the difficulty for me
> was trying to figure out one line that would fit the ongoing narrative
> that is the kernel changelog.
> 
> I was actually surprised when you asked for a full patch, so I just sent
> you a copy of my private commit, with an improved commit message and S-o-b.
> (Should I have added "Cc: stable" to it?)
> 
> But since I now know you prefer even trivial changes like this in formal
> patch form, I'll try to do it right in future.

It's partly for convenience on my part but more to attribute changes
correctly.  This is something you did so if at all possible I'd like
you to take the credit and (however minute it may be) the accompanying
responsibility.  It doesn't have to be perfect and I'm happy to edit
the commit messages / patches as necessary and adding cc to stable.
Well, at least unless you're gonna be submitting large volume of
patches.

Thanks.