[GIT PULL] sh updates for 2.6.33-rc7
Paul Mundt
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(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Grant Likely
> 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
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.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
Paul Mundt
> On Mon, Feb 1, 2010 at 9:06 PM, Paul Mundt <let...@linux-sh.org> wrote:
> > Please pull from:
> >
> >
> > Which contains:
> >
> > Magnus Damm (1):
> >
> > 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).
>
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.
Grant Likely
> On Tue, Feb 02, 2010 at 01:17:49AM -0700, Grant Likely wrote:
>> On Mon, Feb 1, 2010 at 9:06 PM, Paul Mundt <let...@linux-sh.org> wrote:
>> > 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
>>
>> 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.
> 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.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
Paul Mundt
> On Tue, Feb 2, 2010 at 1:21 AM, Paul Mundt <let...@linux-sh.org> wrote:
> > On Tue, Feb 02, 2010 at 01:17:49AM -0700, Grant Likely wrote:
> >> Hold the phone; please coordinate with me before picking up SPI
> >> 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.
>
> > 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.
>
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 :-)
Grant Likely
> 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.