From: David Miller <davem@davemloft.net>
To: khc@pm.waw.pl
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Please pull - generic HDLC
Date: Sun, 12 Oct 2008 14:47:04 -0700 (PDT) [thread overview]
Message-ID: <20081012.144704.39192150.davem@davemloft.net> (raw)
In-Reply-To: <m33aj15xhr.fsf@maximus.localdomain>
From: Krzysztof Halasa <khc@pm.waw.pl>
Date: Sun, 12 Oct 2008 23:12:16 +0200
> David,
>
> The following changes since commit
> f3073ac76755abd63b1d4c3d145f4c15b65b5355 (i.e., your netdev-2.6):
> Guennadi Liakhovetski (1): smc911x: Fix external PHY detection
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/chris/linux-2.6.git for-david
You've missed the networking merge window, as I stated the other
day I'm not taking any more networking changes.
You should have merged this in earlier.
--------------------
Subject: preparing net-next-2.6 for merge...
From: David Miller <davem@davemloft.net>
To: netdev@vger.kernel.org
CC: linux-wireless@vger.kernel.org
Date: Fri, 10 Oct 2008 12:29:37 -0700 (PDT)
X-Mailer: Mew version 6.1 on Emacs 22.1 / Mule 5.0 (SAKAKI)
I'm doing some quick merge, build, and boot tests on the tree as it
stands right now then I'll send a pull request to Linus.
I'm sure there are some things people still wanted to get into the
tree, but let's try to follow the rules this time. Only bug fixes
and corrections at this point forward.
Look at it this way, I have tons of stuff I wasn't able to finish up
in time either, so both the rule and the pain and being applied fairly
:-)
Anyways, just FYI...
next prev parent reply other threads:[~2008-10-12 21:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-12 21:12 Please pull - generic HDLC Krzysztof Halasa
2008-10-12 21:47 ` David Miller [this message]
2008-10-12 22:35 ` Krzysztof Halasa
2008-10-13 5:53 ` Adrian Bunk
2008-10-13 14:53 ` Krzysztof Halasa
2008-10-13 18:23 ` 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=20081012.144704.39192150.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=khc@pm.waw.pl \
--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