From: David Miller <davem@davemloft.net>
To: keil@b1-systems.de
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, i4ldeveloper@listserv.isdn4linux.de,
andreas@eversberg.eu, acme@redhat.com
Subject: Re: [PATCH 0/1] mISDN: Fix handling of receive buffer size in L1oIP
Date: Sun, 02 Aug 2009 13:02:25 -0700 (PDT) [thread overview]
Message-ID: <20090802.130225.53875200.davem@davemloft.net> (raw)
In-Reply-To: <cover.1248781021.git.keil@b1-systems.de>
From: Karsten Keil <keil@b1-systems.de>
Date: Tue, 28 Jul 2009 13:37:01 +0200
> This patch fix a regression introduced in 2.6.31 with the commit
> 8c90e11e3543d7de612194a042a148caeaab5f1d "mISDN: Use kernel_{send,recv}msg instead of open coding".
>
> Linus: you can pull the fix from
> git://git.kernel.org/pub/scm/linux/kernel/git/kkeil/ISDN-2.6-net-next for_linus
>
> David for net-next-2.6 you can get it from:
> git://git.kernel.org/pub/scm/linux/kernel/git/kkeil/ISDN-2.6-net-next for_david
Karsten, please don't send fix incusion requests like this. Either
send them via me always, or bypass me and go straight to Linus
always.
Asking two people to pull the fix in via two different means only
will make for confusion.
If it's a fix, get it into net-2.6 via me, otherwise submit it to
net-next-2.6 if it is not an important fix. Sending it to Linus
and my net-next-2.6 at the same time makes %100 no sense. One
tree is for fixes, and the other is for new development.
If you're worried about fixes propagating and merging properly,
I take care of that completely. When a fix gets into net-2.6
eventually I will merge net-2.6 into net-next-2.6 and that's how
it will show up there. If there is a dependency on new work that
this fix creates, tell me, and I'll do the merge more quickly
for you.
prev parent reply other threads:[~2009-08-02 20:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 11:37 [PATCH 0/1] mISDN: Fix handling of receive buffer size in L1oIP Karsten Keil
2009-07-27 17:24 ` [PATCH 1/1] " Karsten Keil
2009-08-02 20:02 ` David Miller
2009-08-02 20:02 ` David Miller [this message]
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=20090802.130225.53875200.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=acme@redhat.com \
--cc=andreas@eversberg.eu \
--cc=i4ldeveloper@listserv.isdn4linux.de \
--cc=keil@b1-systems.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.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).