From: Andrew Morton <akpm@linux-foundation.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: kkeil@suse.de, isdn4linux@listserv.isdn4linux.de,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
davem@davemloft.net
Subject: Re: [for 2.6.26] ISDN cleanups, ok for upstream?
Date: Fri, 18 Apr 2008 16:41:13 -0700 [thread overview]
Message-ID: <20080418164113.6863213d.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080418225355.GA30189@havoc.gtf.org>
On Fri, 18 Apr 2008 18:53:55 -0400
Jeff Garzik <jeff@garzik.org> wrote:
> I don't know the current state of
> akpm's pull of jgarzik/misc-2.6.git#ALL.
oops. It seems that I disabled it quite a long time ago. I'll resurrect
it.
> The 'isdn-cleanups' branch of
> master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/misc-2.6.git isdn-cleanups
That merges cleanly against the small number of isdn patches which are
pending in -mm, so we're OK from that POV.
next prev parent reply other threads:[~2008-04-18 23:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 22:53 [for 2.6.26] ISDN cleanups, ok for upstream? Jeff Garzik
2008-04-18 23:41 ` Andrew Morton [this message]
2008-04-20 22:20 ` Jeff Garzik
2008-04-19 0:13 ` David Miller
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=20080418164113.6863213d.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=isdn4linux@listserv.isdn4linux.de \
--cc=jeff@garzik.org \
--cc=kkeil@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).