From: Paul Mundt <lethal@linux-sh.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
spi-devel-general@lists.sourceforge.net
Subject: Re: [GIT PULL] sh updates for 2.6.33-rc7
Date: Tue, 02 Feb 2010 08:21:44 +0000 [thread overview]
Message-ID: <20100202082144.GB5716@linux-sh.org> (raw)
In-Reply-To: <fa686aa41002020017m5ea0020di6924905a631dc7d6@mail.gmail.com>
On Tue, Feb 02, 2010 at 01:17:49AM -0700, Grant Likely wrote:
> On Mon, Feb 1, 2010 at 9:06 PM, Paul Mundt <lethal@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 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.
WARNING: multiple messages have this Message-ID (diff)
From: Paul Mundt <lethal@linux-sh.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
spi-devel-general@lists.sourceforge.net
Subject: Re: [GIT PULL] sh updates for 2.6.33-rc7
Date: Tue, 2 Feb 2010 17:21:44 +0900 [thread overview]
Message-ID: <20100202082144.GB5716@linux-sh.org> (raw)
In-Reply-To: <fa686aa41002020017m5ea0020di6924905a631dc7d6@mail.gmail.com>
On Tue, Feb 02, 2010 at 01:17:49AM -0700, Grant Likely wrote:
> On Mon, Feb 1, 2010 at 9:06 PM, Paul Mundt <lethal@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 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.
next prev parent reply other threads:[~2010-02-02 8:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 4:06 [GIT PULL] sh updates for 2.6.33-rc7 Paul Mundt
2010-02-02 4:06 ` Paul Mundt
2010-02-02 8:17 ` Grant Likely
2010-02-02 8:17 ` Grant Likely
2010-02-02 8:21 ` Paul Mundt [this message]
2010-02-02 8:21 ` Paul Mundt
2010-02-02 8:31 ` Grant Likely
2010-02-02 8:31 ` Grant Likely
2010-02-02 8:46 ` Paul Mundt
2010-02-02 8:46 ` Paul Mundt
2010-02-02 13:54 ` Grant Likely
2010-02-02 13:54 ` Grant Likely
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=20100202082144.GB5716@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=torvalds@linux-foundation.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.