From: Oliver Hartkopp <oliver.hartkopp@volkswagen.de>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Rostislav Lisovy <lisovy@gmail.com>,
linux-can@vger.kernel.org, pisa@cmp.felk.cvut.cz,
sojkam1@fel.cvut.cz
Subject: Re: [PATCH 2/2] net/sched: CAN Filter/Classifier
Date: Mon, 04 Jun 2012 10:02:34 +0200 [thread overview]
Message-ID: <4FCC6B9A.4090207@volkswagen.de> (raw)
In-Reply-To: <4FCC6875.80700@pengutronix.de>
On 04.06.2012 09:49, Marc Kleine-Budde wrote:
> On 06/04/2012 09:44 AM, Marc Kleine-Budde wrote:
>> On 06/04/2012 09:14 AM, Oliver Hartkopp wrote:
>>> Hello Rostislav,
>>>
>>> the merge window is closed and net-next is now open.
>>>
>>> Please re-spin you patches based on the can-next tree
>>>
>>> https://gitorious.org/linux-can/linux-can-next
>> I'm not sure, that I'm the correct gateway for net/sched patch.
>
> ...If David takes the patch, it shouldn't be based on linux-can-next
>
Ok, then creating a patch based on net-next and posting them on netdev would
be the better approach - thanks for the clarification.
Do you think linux-can and lartc ML for CC is still a good idea?
Regards,
Oliver
next prev parent reply other threads:[~2012-06-04 8:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 9:12 [PATCH 1/2] can: Added constants containing length of CAN identifiers Rostislav Lisovy
2012-05-25 9:12 ` [PATCH 2/2] net/sched: CAN Filter/Classifier Rostislav Lisovy
2012-06-04 7:14 ` Oliver Hartkopp
2012-06-04 7:44 ` Marc Kleine-Budde
2012-06-04 7:49 ` Marc Kleine-Budde
2012-06-04 8:02 ` Oliver Hartkopp [this message]
2012-06-04 8:04 ` Marc Kleine-Budde
2012-05-25 9:22 ` [PATCH 1/2] can: Added constants containing length of CAN identifiers David Miller
2012-05-25 10:44 ` Rostislav Lisovy
-- strict thread matches above, loose matches on Subject: below --
2012-06-04 16:09 [PATCH 1/2] can: Add " Rostislav Lisovy
2012-06-04 16:09 ` [PATCH 2/2] net/sched: CAN Filter/Classifier Rostislav Lisovy
2012-06-05 8:09 ` Eric Dumazet
2012-06-07 9:53 ` Rostislav Lisovy
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=4FCC6B9A.4090207@volkswagen.de \
--to=oliver.hartkopp@volkswagen.de \
--cc=linux-can@vger.kernel.org \
--cc=lisovy@gmail.com \
--cc=mkl@pengutronix.de \
--cc=pisa@cmp.felk.cvut.cz \
--cc=sojkam1@fel.cvut.cz \
/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.