From: Jeff Garzik <jeff@garzik.org>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHes] pull request: WAN
Date: Tue, 22 Jul 2008 17:39:53 -0400 [thread overview]
Message-ID: <488653A9.50001@garzik.org> (raw)
In-Reply-To: <m3ljzyc9e7.fsf@maximus.localdomain>
Krzysztof Halasa wrote:
> Hi Jeff,
>
> Please pull from:
> git://git.kernel.org/pub/scm/linux/kernel/git/chris/linux-2.6.git hdlc
>
> This is based on pure v2.6.26 and includes various WAN cleanups as
> well as LMC, Zilog (hostess_sv11 + sealevel = z85230) and Cosa drivers
> ported from syncppp to generic HDLC. I have no hardware for that so -
> untested.
>
> This makes hdlc-ppp the only user of syncppp.
>
> My plan is to replace hdlc-ppp and syncppp with the new hdlc-ppp, hope
> that's now ok with syncppp going.
>
> The long-term plan is to also add generic PPP interface so users can
> do PPP auth, compression and what not. 2.6.30+ maybe.
>
> I have tried to test-merge your upstream-next branch and it causes
> conflicts in drivers/net/wan/pc300_drv.c (a trivial one) and
> net/netfilter/nf_conntrack_proto_tcp.c (some pre-2.6.26 thing I
> guess).
>
> The first commits in my tree (after v2.6.26) are already in your tree,
> you've got them by mail. It seems that git knows that.
Anything in upstream-next went upstream, and so we need to apply this on
top of the current Linus upstream (torvalds/linux-2.6.git) at the very
least.
Would you mind doing that, please?
Also, git pulls are great, but it would be helpful if you supply a
git-shortlog summary of the changes, and the patch (>400k will only go
to me, list will ignore).
Jeff
next prev parent reply other threads:[~2008-07-22 21:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-19 13:04 [PATCHes] pull request: WAN Krzysztof Halasa
2008-07-22 21:39 ` Jeff Garzik [this message]
2008-07-23 21:31 ` Krzysztof Halasa
2008-07-23 21:38 ` Krzysztof Halasa
2008-08-02 17:50 ` Krzysztof Halasa
2008-08-07 8:06 ` Jeff Garzik
2008-08-08 11:18 ` Krzysztof Halasa
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=488653A9.50001@garzik.org \
--to=jeff@garzik.org \
--cc=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;
as well as URLs for NNTP newsgroup(s).