From: "Søren Holm" <sgh@sgh.dk>
To: Christian Riesch <christian.riesch@omicron.at>
Cc: netdev@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] asix: Support DLink DUB-E100 H/W Ver C1
Date: Tue, 18 Sep 2012 10:40:48 +0200 [thread overview]
Message-ID: <1731301.juso6zgXvT@koontz> (raw)
In-Reply-To: <CABkLObq3jQG_KMRrNpYGsseJrCYQ08cJfQFD5fpTmYDyDMGROA@mail.gmail.com>
Tirsdag den 18. september 2012 10:21:17 skrev Christian Riesch:
> IIRC this is not how it works. Your patch must go into the current
> mainline kernel first (via net or net-next) before, then it will be
> backported to the stable series.Therefore you must always send patches
> that apply to net, or net-next...
> Christian
I'm aware of that now, thanks :)
--
Søren Holm
next prev parent reply other threads:[~2012-09-18 8:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 19:23 [PATCH] asix: Support DLink DUB-E100 H/W Ver C1 Søren Holm
2012-09-18 5:41 ` Christian Riesch
2012-09-18 7:49 ` Søren Holm
2012-09-18 8:21 ` Christian Riesch
2012-09-18 8:40 ` Søren Holm [this message]
2012-09-18 7:50 ` Søren Holm
2012-09-19 21:21 ` 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=1731301.juso6zgXvT@koontz \
--to=sgh@sgh.dk \
--cc=christian.riesch@omicron.at \
--cc=netdev@vger.kernel.org \
--cc=stable@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).