On Tue, Sep 15, 2009 at 19:15, Andrew Morton wrote:
> blackfin-convert-to-use-arch_gettimeoffset.patch
i thought John was merging this via some sort of patch series, but i
can pick it up in the Blackfin tree to make sure things are really
sane
> blackfin-fix-read-buffer-overflow.patch
the latter patch i merged into my tree (and i thought that i followed
up in the original posting about this)
> checkpatch-possible-types-else-cannot-start-a-type.patch
> checkpatch-handle-c99-comments-correctly-performance-issue.patch
> checkpatch-indent-checks-stop-when-we-run-out-of-continuation-lines.patch
> checkpatch-make-f-alias-file-add-help-more-verbose-help-message.patch
> checkpatch-format-strings-should-not-have-brackets-in-macros.patch
> checkpatch-limit-sn-un-matches-to-actual-bit-sizes.patch
> checkpatch-version-029.patch
> checkpatch-add-some-common-blackfin-checks.patch
>
> Grumpy. These spit perl warnings but maintainer won't talk to me.
the last one shouldnt cause any warnings at all ;)
-mike
On Tue, 15 Sep 2009 23:56:21 -0400 Mike Frysinger <[email protected]> wrote:
> On Tue, Sep 15, 2009 at 19:15, Andrew Morton wrote:
> > blackfin-convert-to-use-arch_gettimeoffset.patch
>
> i thought John was merging this via some sort of patch series, but i
> can pick it up in the Blackfin tree to make sure things are really
> sane
Sent.
> > blackfin-fix-read-buffer-overflow.patch
>
> the latter patch i merged into my tree (and i thought that i followed
> up in the original posting about this)
Well, it isn't in linux-next so as far as I'm concerned I have the
only copy. Should you be getting your tree into linux-next?
On Wed, Sep 16, 2009 at 00:18, Andrew Morton wrote:
> On Tue, 15 Sep 2009 23:56:21 -0400 Mike Frysinger wrote:
>> On Tue, Sep 15, 2009 at 19:15, Andrew Morton wrote:
>> > blackfin-fix-read-buffer-overflow.patch
>>
>> the latter patch i merged into my tree (and i thought that i followed
>> up in the original posting about this)
>
> Well, it isn't in linux-next so as far as I'm concerned I have the
> only copy. Should you be getting your tree into linux-next?
not sure how the next process works. what do i need to do Stephen ?
-mike
Hi Andrew, Mike,
On Tue, 15 Sep 2009 21:18:10 -0700 Andrew Morton <[email protected]> wrote:
>
> On Tue, 15 Sep 2009 23:56:21 -0400 Mike Frysinger <[email protected]> wrote:
>
> > On Tue, Sep 15, 2009 at 19:15, Andrew Morton wrote:
> > > blackfin-convert-to-use-arch_gettimeoffset.patch
> >
> > i thought John was merging this via some sort of patch series, but i
> > can pick it up in the Blackfin tree to make sure things are really
> > sane
>
> Sent.
>
> > > blackfin-fix-read-buffer-overflow.patch
> >
> > the latter patch i merged into my tree (and i thought that i followed
> > up in the original posting about this)
>
> Well, it isn't in linux-next so as far as I'm concerned I have the
> only copy. Should you be getting your tree into linux-next?
There is a blackfin tree in linux-next managed by Bryan Wu:
git://git.kernel.org/pub/scm/linux/kernel/git/cooloney/blackfin-2.6.git#for-linus
As far as I can tell, it hasn't bee updated since March 30.
--
Cheers,
Stephen Rothwell [email protected]
http://www.canb.auug.org.au/~sfr/
Hi Mike,
On Wed, 16 Sep 2009 00:24:37 -0400 Mike Frysinger <[email protected]> wrote:
>
> not sure how the next process works. what do i need to do Stephen ?
You send me a request for inclusion with a git tree (and branch) (or
quilt series on a web site) and contact address(es) and understand the
following:
Thanks for adding your subsystem tree as a participant of linux-next. As
you may know, this is not a judgment of your code. The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window.
You will need to ensure that the patches/commits in your tree/series have
been:
* submitted under GPL v2 (or later) and include the Contributor's
Signed-off-by,
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.
Basically, this should be just what you would send to Linus (or ask him
to fetch). It is allowed to be rebased if you deem it necessary.
--
Cheers,
Stephen Rothwell
[email protected]
Legal Stuff:
By participating in linux-next, your subsystem tree contributions are
public and will be included in the linux-next trees. You may be sent
e-mail messages indicating errors or other issues when the
patches/commits from your subsystem tree are merged and tested in
linux-next. These messages may also be cross-posted to the linux-next
mailing list, the linux-kernel mailing list, etc. The linux-next tree
project and IBM (my employer) make no warranties regarding the linux-next
project, the testing procedures, the results, the e-mails, etc. If you
don't agree to these ground rules, let me know and I'll remove your tree
from participation in linux-next.
On Wed, Sep 16, 2009 at 02:06, Stephen Rothwell wrote:
> On Wed, 16 Sep 2009 00:24:37 -0400 Mike Frysinger wrote:
>> not sure how the next process works. what do i need to do Stephen ?
>
> You send me a request for inclusion with a git tree (and branch) (or
> quilt series on a web site) and contact address(es) and understand the
> following:
ok, please replace the current Blackfin tree:
git://git.kernel.org/pub/scm/linux/kernel/git/cooloney/blackfin-2.6.git#for-linus
with my Blackfin tree:
git://git.kernel.org/pub/scm/linux/kernel/git/vapier/blackfin.git#for-linus
and i'll try to keep it updated
-mike
Hi Mike,
On Wed, 16 Sep 2009 08:53:46 -0400 Mike Frysinger <[email protected]> wrote:
>
> ok, please replace the current Blackfin tree:
> git://git.kernel.org/pub/scm/linux/kernel/git/cooloney/blackfin-2.6.git#for-linus
> with my Blackfin tree:
> git://git.kernel.org/pub/scm/linux/kernel/git/vapier/blackfin.git#for-linus
>
> and i'll try to keep it updated
Done. It will be in tomorrow's linux-next.
--
Cheers,
Stephen Rothwell [email protected]
http://www.canb.auug.org.au/~sfr/