Skip to contentSkip to conversation

sh updates for 2.6.33-rc7

GIT PULL Paul Mundt 2 participants 6 messages Feb 2, 2010

Subsystems (2)
SPI SuperH
lore
Share & tools
lore

Paul Mundt

author
#0 lore raw

Please pull from:

	master.kernel.org:/pub/scm/linux/kernel/git/lethal/sh-2.6.git sh/for-2.6.33

Which contains:

Magnus Damm (1):
usb: r8a66597-hdc disable interrupts fix

Marek Skuczynski (2):
sh: Fix access to released memory in dwarf_unwinder_cleanup()
sh: Fix access to released memory in clk_debugfs_register_one()

Markus Pietrek (1):
spi: spi_sh_msiof: Fixed data sampling on the correct edge

 arch/sh/kernel/cpu/clock.c      |    4 ++--
 arch/sh/kernel/dwarf.c          |    8 ++++----
 drivers/spi/spi_sh_msiof.c      |   15 ++++++---------
 drivers/usb/host/r8a66597-hcd.c |   17 ++++++++++++++++-
 4 files changed, 28 insertions(+), 16 deletions(-)
#1 lore raw
Quoted 9 lines · Paul Mundt

Please pull from:

       master.kernel.org:/pub/scm/linux/kernel/git/lethal/sh-2.6.git sh/for-2.6.33

Which contains:

Magnus Damm (1):
     usb: r8a66597-hdc disable interrupts fix

Quoted 6 lines

Marek Skuczynski (2):
     sh: Fix access to released memory in dwarf_unwinder_cleanup()
     sh: Fix access to released memory in clk_debugfs_register_one()

Markus Pietrek (1):
     spi: spi_sh_msiof: Fixed data sampling on the correct edge

Hold the phone; please coordinate with me before picking up SPI patches into your tree. I don't mind arch specific spi changes going in via a different tree, but I'd like to know about it before I waste time farting around with the same patch (like I did with this one tonight, and only found out that you also picked it up when I came across this pull request by chance).

g.

Signature · 2 lines
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
author
#2 lore raw
Quoted 17 lines · Grant Likely
Quoted 9 lines · Paul Mundt

Please pull from:

? ? ? ?master.kernel.org:/pub/scm/linux/kernel/git/lethal/sh-2.6.git sh/for-2.6.33

Which contains:

Magnus Damm (1):
? ? ?usb: r8a66597-hdc disable interrupts fix

Quoted 6 lines

Marek Skuczynski (2):
? ? ?sh: Fix access to released memory in dwarf_unwinder_cleanup() ? ? ?sh: Fix access to released memory in clk_debugfs_register_one()

Markus Pietrek (1):
? ? ?spi: spi_sh_msiof: Fixed data sampling on the correct edge

Quoted 7 lines

Hold the phone; please coordinate with me before picking up SPI patches into your tree. I don't mind arch specific spi changes going in via a different tree, but I'd like to know about it before I waste time farting around with the same patch (like I did with this one tonight, and only found out that you also picked it up when I came across this pull request by chance).

If there's someone actively looking after the SPI stuff then that's fine. I didn't bother bouncing this one off of the SPI list since it's a hardware-specific correctness fix and has no dependency on anything subsystem related.

#3 lore raw
Quoted 18 lines · Paul Mundt
Quoted 17 lines · Grant Likely
Quoted 15 lines · Paul Mundt

Please pull from:

? ? ? ?master.kernel.org:/pub/scm/linux/kernel/git/lethal/sh-2.6.git sh/for-2.6.33

Which contains:

Magnus Damm (1):
? ? ?usb: r8a66597-hdc disable interrupts fix

Marek Skuczynski (2):
? ? ?sh: Fix access to released memory in dwarf_unwinder_cleanup() ? ? ?sh: Fix access to released memory in clk_debugfs_register_one()

Markus Pietrek (1):
? ? ?spi: spi_sh_msiof: Fixed data sampling on the correct edge

Quoted 8 lines
Quoted 7 lines

Hold the phone; please coordinate with me before picking up SPI patches into your tree.  I don't mind arch specific spi changes going in via a different tree, but I'd like to know about it before I waste time farting around with the same patch (like I did with this one tonight, and only found out that you also picked it up when I came across this pull request by chance).

If there's someone actively looking after the SPI stuff then that's fine.

I am now. There wasn't anyone for a while.

Quoted 3 lines

I didn't bother bouncing this one off of the SPI list since it's a hardware-specific correctness fix and has no dependency on anything subsystem related.

Fair enough, but the patch itself came across the SPI list, and so it showed up in the patchwork tracking of spi-devel-general which I'm using to keep on top of everything. I brief reply to the patch email would have let me know that I didn't have to waste any time with it.

Thanks,
g.

Signature · 2 lines
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
author
#4 lore raw
Quoted 13 lines · Grant Likely
Quoted 9 lines · Paul Mundt
Quoted 7 lines · Grant Likely

Hold the phone; please coordinate with me before picking up SPI patches into your tree. ?I don't mind arch specific spi changes going in via a different tree, but I'd like to know about it before I waste time farting around with the same patch (like I did with this one tonight, and only found out that you also picked it up when I came across this pull request by chance).

If there's someone actively looking after the SPI stuff then that's fine.

I am now. There wasn't anyone for a while.

Quoted 9 lines
Quoted 3 lines

I didn't bother bouncing this one off of the SPI list since it's a hardware-specific correctness fix and has no dependency on anything subsystem related.

Fair enough, but the patch itself came across the SPI list, and so it showed up in the patchwork tracking of spi-devel-general which I'm using to keep on top of everything. I brief reply to the patch email would have let me know that I didn't have to waste any time with it.

Ahh.. this is where the confusion came from. The initial version of the patch was only posted to the sh list, Magnus asked for it to be reposted to the spi list and I hadn't heard anything about it since then, so I assumed the poster just disappeared and I just cleaned it up and applied it by hand. Apparently it was reposted but the sh list was dropped, so I never saw the updated version. If I had known that it had hit the SPI list I would have followed up there, I'll be more careful next time now that I know someone is paying attention :-)

#5 lore raw
Quoted 8 lines · Paul Mundt

Ahh.. this is where the confusion came from. The initial version of the patch was only posted to the sh list, Magnus asked for it to be reposted to the spi list and I hadn't heard anything about it since then, so I assumed the poster just disappeared and I just cleaned it up and applied it by hand. Apparently it was reposted but the sh list was dropped, so I never saw the updated version. If I had known that it had hit the SPI list I would have followed up there, I'll be more careful next time now that I know someone is paying attention :-)

:-) Thanks.

g.