From: Pavel Machek <pavel@suse.cz>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Pavel Machek <pavel@ucw.cz>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: include order for i2c-amd8111
Date: Wed, 8 Jan 2003 13:06:59 +0100 [thread overview]
Message-ID: <20030108120658.GB592@zaurus> (raw)
In-Reply-To: <20030107114403.A5029@ucw.cz>
Hi!
> > > It seems all linux then all asm is prefered order...
> > > > > Yes, but not for any great reason, AFAICT. I think this comes under
> > the "too trivial" rule (ie. I'll accept it from the author, but not
> > someone else).
>
> The author (me ;) definitely doesn't mind you applying the patch, but
> would prefer if the one who pushed the 8111 driver into the kernel
> (Pavel) would update it to the version found in lm_sensors 2.7.0 at the
> same time.
Do you think you can mail me that file?
Pavel
--
Pavel
Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...
prev parent reply other threads:[~2003-01-10 18:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-05 23:13 include order for i2c-amd8111 Pavel Machek
2003-01-06 0:40 ` Rusty Russell
2003-01-07 10:44 ` Vojtech Pavlik
2003-01-08 12:06 ` Pavel Machek [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=20030108120658.GB592@zaurus \
--to=pavel@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rusty@rustcorp.com.au \
--cc=vojtech@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox