From: Simon Guinot <simon.guinot@sequanux.org>
To: Jason Cooper <jason@lakedaemon.net>
Cc: Jeff Garzik <jgarzik@redhat.com>, Tejun Heo <tj@kernel.org>,
linux-ide@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@free-electrons.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Lior Amsalem <alior@marvell.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v2 0/3] Fix SATA disk hotplug for Armada 370/XP SoCs
Date: Tue, 14 Jan 2014 16:48:34 +0100 [thread overview]
Message-ID: <20140114154834.GD32507@kw.sim.vm.gnt> (raw)
In-Reply-To: <20140114151404.GN19878@titan.lakedaemon.net>
[-- Attachment #1: Type: text/plain, Size: 2296 bytes --]
On Tue, Jan 14, 2014 at 10:14:04AM -0500, Jason Cooper wrote:
> Simon,
>
> On Tue, Jan 14, 2014 at 03:50:04PM +0100, Simon Guinot wrote:
> > Hello,
> >
> > This patch series fixes a SATA disk hotplug issue for the Armada 370/XP
> > SoCs: once a disk is removed from a SATA port, then the re-plug events
> > are not detected by the sata_mv driver.
> >
> > This should be applied to the -stable kernels 3.10 and onwards.
>
> Please add a 'Fixes: <commit-hash> (oneline)' tag below the Cc: stable
> tags. It looks like the sata_mv binding and the Armada 370 DT booting
> were both introduced in v3.6, so I would probably use:
>
> Fixes: 9ae6f740b49f (arm: mach-mvebu: add support for Armada 370 and Armada XP with DT)
Hi Jason,
I am not comfortable with this "Fixes: commit_id" notation. It states
that the patch fixes a regression introduced by a given commit. This
hardly makes sense to me because obviously the hotplug issue has not
been introduced by:
"arm: mach-mvebu: add support for Armada 370 and Armada XP with DT".
I know that the purpose is purely administrative, but it is kind of
weird...
>
> Is there a specific reason you say v3.10?
I could have said nothing as well.
As stable kernel older than 3.10 are no longer maintained, I think
we don't need to point out a specific commit as a -stable target.
Simply Cc'ing -stable without any extra informations should be good
enough.
>
> Once you've incorporated Gregory's comments,
>
> Acked-by: Jason Cooper <jason@lakedaemon.net>
OK.
Thanks,
Simon
>
> > Lior Amsalem (1):
> > ata: sata_mv: fix disk hotplug for Armada 370/XP SoCs
> >
> > Simon Guinot (2):
> > ata: sata_mv: introduce compatible string "marvell,armada-370-xp-sata"
> > ARM: mvebu: update the SATA compatible string for Armada 370/XP
> >
> > Documentation/devicetree/bindings/ata/marvell.txt | 2 +-
> > arch/arm/boot/dts/armada-370-xp.dtsi | 2 +-
> > drivers/ata/sata_mv.c | 25 +++++++++++++++++++++++
> > 3 files changed, 27 insertions(+), 2 deletions(-)
>
> Tejun,
>
> I see no point to breaking up this series only to have both pieces end
> up in stable. Are you ok with taking the whole thing?
>
> thx,
>
> Jason.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: simon.guinot@sequanux.org (Simon Guinot)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] Fix SATA disk hotplug for Armada 370/XP SoCs
Date: Tue, 14 Jan 2014 16:48:34 +0100 [thread overview]
Message-ID: <20140114154834.GD32507@kw.sim.vm.gnt> (raw)
In-Reply-To: <20140114151404.GN19878@titan.lakedaemon.net>
On Tue, Jan 14, 2014 at 10:14:04AM -0500, Jason Cooper wrote:
> Simon,
>
> On Tue, Jan 14, 2014 at 03:50:04PM +0100, Simon Guinot wrote:
> > Hello,
> >
> > This patch series fixes a SATA disk hotplug issue for the Armada 370/XP
> > SoCs: once a disk is removed from a SATA port, then the re-plug events
> > are not detected by the sata_mv driver.
> >
> > This should be applied to the -stable kernels 3.10 and onwards.
>
> Please add a 'Fixes: <commit-hash> (oneline)' tag below the Cc: stable
> tags. It looks like the sata_mv binding and the Armada 370 DT booting
> were both introduced in v3.6, so I would probably use:
>
> Fixes: 9ae6f740b49f (arm: mach-mvebu: add support for Armada 370 and Armada XP with DT)
Hi Jason,
I am not comfortable with this "Fixes: commit_id" notation. It states
that the patch fixes a regression introduced by a given commit. This
hardly makes sense to me because obviously the hotplug issue has not
been introduced by:
"arm: mach-mvebu: add support for Armada 370 and Armada XP with DT".
I know that the purpose is purely administrative, but it is kind of
weird...
>
> Is there a specific reason you say v3.10?
I could have said nothing as well.
As stable kernel older than 3.10 are no longer maintained, I think
we don't need to point out a specific commit as a -stable target.
Simply Cc'ing -stable without any extra informations should be good
enough.
>
> Once you've incorporated Gregory's comments,
>
> Acked-by: Jason Cooper <jason@lakedaemon.net>
OK.
Thanks,
Simon
>
> > Lior Amsalem (1):
> > ata: sata_mv: fix disk hotplug for Armada 370/XP SoCs
> >
> > Simon Guinot (2):
> > ata: sata_mv: introduce compatible string "marvell,armada-370-xp-sata"
> > ARM: mvebu: update the SATA compatible string for Armada 370/XP
> >
> > Documentation/devicetree/bindings/ata/marvell.txt | 2 +-
> > arch/arm/boot/dts/armada-370-xp.dtsi | 2 +-
> > drivers/ata/sata_mv.c | 25 +++++++++++++++++++++++
> > 3 files changed, 27 insertions(+), 2 deletions(-)
>
> Tejun,
>
> I see no point to breaking up this series only to have both pieces end
> up in stable. Are you ok with taking the whole thing?
>
> thx,
>
> Jason.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140114/e6b03fc5/attachment.sig>
next prev parent reply other threads:[~2014-01-14 15:48 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 14:50 [PATCH v2 0/3] Fix SATA disk hotplug for Armada 370/XP SoCs Simon Guinot
2014-01-14 14:50 ` Simon Guinot
2014-01-14 14:50 ` [PATCH v2 1/3] ata: sata_mv: introduce compatible string "marvell,armada-370-xp-sata" Simon Guinot
2014-01-14 14:50 ` [PATCH v2 1/3] ata: sata_mv: introduce compatible string "marvell, armada-370-xp-sata" Simon Guinot
2014-01-14 14:59 ` [PATCH v2 1/3] ata: sata_mv: introduce compatible string "marvell,armada-370-xp-sata" Gregory CLEMENT
2014-01-14 14:59 ` [PATCH v2 1/3] ata: sata_mv: introduce compatible string "marvell, armada-370-xp-sata" Gregory CLEMENT
2014-01-14 14:50 ` [PATCH v2 2/3] ata: sata_mv: fix disk hotplug for Armada 370/XP SoCs Simon Guinot
2014-01-14 14:50 ` Simon Guinot
2014-01-26 7:32 ` Thomas Petazzoni
2014-01-26 7:32 ` Thomas Petazzoni
2014-01-31 10:46 ` Simon Guinot
2014-01-31 10:46 ` Simon Guinot
2014-01-31 10:54 ` Thomas Petazzoni
2014-01-31 10:54 ` Thomas Petazzoni
2014-01-14 14:50 ` [PATCH v2 3/3] ARM: mvebu: update the SATA compatible string for Armada 370/XP Simon Guinot
2014-01-14 14:50 ` Simon Guinot
2014-01-14 14:58 ` Gregory CLEMENT
2014-01-14 14:58 ` Gregory CLEMENT
2014-01-14 15:14 ` [PATCH v2 0/3] Fix SATA disk hotplug for Armada 370/XP SoCs Jason Cooper
2014-01-14 15:14 ` Jason Cooper
2014-01-14 15:21 ` Tejun Heo
2014-01-14 15:21 ` Tejun Heo
2014-01-14 15:22 ` Tejun Heo
2014-01-14 15:22 ` Tejun Heo
2014-01-14 15:28 ` Russell King - ARM Linux
2014-01-14 15:28 ` Russell King - ARM Linux
2014-01-14 15:48 ` Simon Guinot [this message]
2014-01-14 15:48 ` Simon Guinot
2014-01-14 15:50 ` Andrew Lunn
2014-01-14 15:50 ` Andrew Lunn
2014-01-14 15:52 ` Tejun Heo
2014-01-14 15:52 ` Tejun Heo
2014-01-14 15:59 ` Jason Cooper
2014-01-14 15:59 ` Jason Cooper
2014-01-14 16:08 ` Jason Cooper
2014-01-14 16:08 ` Jason Cooper
2014-01-14 16:20 ` Luis Henriques
2014-01-14 16:20 ` Luis Henriques
2014-01-14 23:15 ` Simon Guinot
2014-01-14 23:15 ` Simon Guinot
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=20140114154834.GD32507@kw.sim.vm.gnt \
--to=simon.guinot@sequanux.org \
--cc=alior@marvell.com \
--cc=andrew@lunn.ch \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=jgarzik@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ide@vger.kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=stable@vger.kernel.org \
--cc=thomas.petazzoni@free-electrons.com \
--cc=tj@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 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.