From: Kurt Van Dijck <kurt.van.dijck@eia.be>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [net-next-2.6 PATCH v2] allow access to sysfs_groups member
Date: Sat, 21 Nov 2009 12:47:57 +0100 [thread overview]
Message-ID: <20091121114755.GA2693@e-circ.dyndns.org> (raw)
In-Reply-To: <m1d43dtavj.fsf@fess.ebiederm.org>
On Fri, Nov 20, 2009 at 08:32:48AM -0800, Eric W. Biederman wrote:
>
> Kurt Van Dijck <kurt.van.dijck@eia.be> writes:
>
> >> In this case please look at how I modified the bonding driver to do
> >> what you are trying to do. That is the conflict in net-next and
> >> I think it was actually less code.
>
> > It _is_ less code (does a little less too :-) ).
> > It solves the problem anyway. I'll stop with my patch.
>
> You were just worried about CAN devices and not all network devices
> correct?
Yes, but even not _every_ CAN device. It's driver dependant issue.
>
> Eric
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-11-21 11:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 10:51 [net-next-2.6 PATCH] allow access to sysfs_groups member Kurt Van Dijck
2009-11-13 22:27 ` Stephen Hemminger
2009-11-14 16:54 ` [net-next-2.6 PATCH v2] " Kurt Van Dijck
2009-11-16 16:46 ` Stephen Hemminger
2009-11-17 16:21 ` Kurt Van Dijck
2009-11-18 15:43 ` Kurt Van Dijck
2009-11-18 16:08 ` David Miller
2009-11-18 16:41 ` Kurt Van Dijck
2009-11-18 17:57 ` David Miller
2009-11-18 20:57 ` Kurt Van Dijck
2009-11-18 20:59 ` Kurt Van Dijck
2009-11-18 21:08 ` David Miller
2009-11-18 21:42 ` Kurt Van Dijck
2009-11-20 1:11 ` Eric W. Biederman
2009-11-20 10:21 ` Kurt Van Dijck
2009-11-20 16:32 ` Eric W. Biederman
2009-11-21 11:47 ` Kurt Van Dijck [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=20091121114755.GA2693@e-circ.dyndns.org \
--to=kurt.van.dijck@eia.be \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--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).