From: ebiederm@xmission.com (Eric W. Biederman)
To: Kurt Van Dijck <kurt.van.dijck@eia.be>
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: Thu, 19 Nov 2009 17:11:45 -0800 [thread overview]
Message-ID: <m1vdh6t2y6.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <20091118214226.GA283@e-circ.dyndns.org> (Kurt Van Dijck's message of "Wed\, 18 Nov 2009 22\:42\:26 +0100")
Kurt Van Dijck <kurt.van.dijck@eia.be> writes:
> On Wed, Nov 18, 2009 at 01:08:59PM -0800, David Miller wrote:
>>
>> Unfortunately, the code in this function is much different
>> in net-next-2.6 which is where I want to add this, and your
>> patch doesn't apply.
>>
>> Please rebase your patch on that tree, thank you.
> As I mentioned, I'm not experienced with using git yet.
> Is there a fine manual I can inspect? I get lost in the man-pages.
git clone git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next-2.6.git
Should get you started.
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.
The other very useful command is: git log -u some/path/
Git has fine manual pages and git command --help works for the builtin
git commands.
Eric
next prev parent reply other threads:[~2009-11-20 1:11 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 [this message]
2009-11-20 10:21 ` Kurt Van Dijck
2009-11-20 16:32 ` Eric W. Biederman
2009-11-21 11:47 ` Kurt Van Dijck
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=m1vdh6t2y6.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=davem@davemloft.net \
--cc=kurt.van.dijck@eia.be \
--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).