From: David Miller <davem@davemloft.net>
To: vapier@gentoo.org
Cc: linux-kernel@vger.kernel.org, uclinux-dist-devel@blackfin.uclinux.org
Subject: Re: [PATCH 0/7] Blackfin fixes for 2.6.30
Date: Tue, 26 May 2009 02:26:59 -0700 (PDT) [thread overview]
Message-ID: <20090526.022659.11431807.davem@davemloft.net> (raw)
In-Reply-To: <1243329356-12644-1-git-send-email-vapier@gentoo.org>
From: Mike Frysinger <vapier@gentoo.org>
Date: Tue, 26 May 2009 05:15:49 -0400
> Sorry for being so late, but our previous Blackfin maintainer has moved
> on, so we've been working at picking up the slack.
>
> So the stuff here for 2.6.30 is just simple build fixes, gitignore tweaks,
> MAINTAINER updates, and hooking up the new pread syscalls (which was posted
> a while ago already).
Several problems:
1) 10 patches is way too much this late in the 2.6.30 release process.
Pick 1 or 2 that are the most critical and submit those for 2.6.30,
the rest get queued up for 2.6.31
2) Networking patches must have netdev@vger.kernel.org at least
CC:'d so that your patches get properly traced at:
http://patchwork.ozlabs.org/project/netdev/list/
Thank you.
next prev parent reply other threads:[~2009-05-26 9:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 9:15 Mike Frysinger
2009-05-26 9:15 ` [PATCH 1/7] bfin_mac: fix build error due to net_device_ops convert Mike Frysinger
2009-05-26 9:15 ` [PATCH 2/7] Blackfin: hook up preadv/pwritev syscalls Mike Frysinger
2009-05-26 9:15 ` [PATCH 3/7] MAINTAINERS: update Blackfin items Mike Frysinger
2009-05-26 9:15 ` [PATCH 4/7] MAINTAINERS: drop (subscribers-only) markings on Blackfin lists Mike Frysinger
2009-05-26 9:15 ` [PATCH 5/7] Blackfin: ignore generated vmlinux.lds Mike Frysinger
2009-05-26 9:15 ` [PATCH 6/7] Blackfin: drop unneeded asm/.gitignore Mike Frysinger
2009-05-26 9:15 ` [PATCH 7/7] Blackfin: fix strncmp.o build error Mike Frysinger
2009-05-26 9:26 ` David Miller [this message]
2009-05-26 9:28 ` [PATCH 0/7] Blackfin fixes for 2.6.30 David Miller
2009-05-26 9:30 ` Mike Frysinger
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=20090526.022659.11431807.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=vapier@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®