From: Francois Romieu <romieu@fr.zoreil.com>
To: Bjarke Istrup Pedersen <gurligebis@gentoo.org>
Cc: netdev@vger.kernel.org, rl@hellgate.ch,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH net-next 1/7] via-rhine: factor out tx_thresh handling
Date: Sun, 8 Jan 2012 10:39:06 +0100 [thread overview]
Message-ID: <20120108093906.GA28125@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <CACPM=kVKm1xYnBGJ_-ABaBkLcSApnixagQhqmgi89OfCTn5ktQ@mail.gmail.com>
Bjarke Istrup Pedersen <gurligebis@gentoo.org> :
[...]
> Still net-next, or should they be applied on top of mainline 3.2? :)
The base commit is common to davem-next and linus branches. It is an
ancestor of davem's stable branch as well. The patch should thus apply
everywhere the same and rebase automagically... for some time.
--
Ueimor
next prev parent reply other threads:[~2012-01-08 9:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-07 22:48 [PATCH net-next 0/7] via-rhine NAPI rework and misc Francois Romieu
2012-01-07 22:49 ` [PATCH net-next 1/7] via-rhine: factor out tx_thresh handling Francois Romieu
2012-01-08 4:41 ` Bjarke Istrup Pedersen
2012-01-08 5:13 ` Bjarke Istrup Pedersen
2012-01-08 9:39 ` Francois Romieu [this message]
2012-01-07 22:50 ` [PATCH net-next 2/7] via-rhine: balance interrupt acknowledge and events retrieval Francois Romieu
2012-01-07 22:50 ` [PATCH net-next 3/7] via-rhine: remove useless forward declarations Francois Romieu
2012-01-07 22:51 ` [PATCH net-next 4/7] via-rhine: move work from irq handler to softirq and beyond Francois Romieu
2012-01-07 22:51 ` [PATCH net-next 5/7] via-rhine: RHINE_WAIT_FOR macro removal Francois Romieu
2012-01-07 22:52 ` [PATCH net-next 6/7] via-rhine: per device debug level Francois Romieu
2012-01-07 22:52 ` [PATCH net-next 7/7] via-rhine: rework suspend and resume Francois Romieu
2012-01-08 11:57 ` [PATCH net-next 0/7] via-rhine NAPI rework and misc Bjarke Istrup Pedersen
2012-01-10 22:55 ` 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=20120108093906.GA28125@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=davem@davemloft.net \
--cc=gurligebis@gentoo.org \
--cc=netdev@vger.kernel.org \
--cc=rl@hellgate.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.