From: Dave Olien <dmo@osdl.org>
To: Daniel Phillips <phillips@arcor.de>
Cc: axboe@suse.de, _deepfire@mail.ru, linux-kernel@vger.kernel.org
Subject: Re: DAC960 in 2.5.38, with new changes
Date: Mon, 23 Sep 2002 15:03:02 -0700 [thread overview]
Message-ID: <20020923150302.A16033@acpi.pdx.osdl.net> (raw)
In-Reply-To: <E17tb9H-0003d7-00@starship>; from phillips@arcor.de on Mon, Sep 23, 2002 at 11:53:47PM +0200
By the way, I don't know how extensive your code reviewing
of my changes has been.
This morning I sent you the complete driver patch from 2.5.38
to the latest version of the driver. That contains all of
the changes I sent you last week, plus new ones.
Would it be better for me to send you incremental patches
in the future? I could instead generate a patch relative to the
previous version of the driver I sent you.
Let me know what works better for you, based on where you are in code
reviewing.
Thanks!
On Mon, Sep 23, 2002 at 11:53:47PM +0200, Daniel Phillips wrote:
> On Monday 23 September 2002 23:41, Dave Olien wrote:
> > On Mon, Sep 23, 2002 at 10:39:00PM +0200, Daniel Phillips wrote:
> > > Minor whitespace suggestion: don't worry too much about breaking up
> > > lines to fit in 80 columns. It's nice where it works, but where it
> > > just makes more lines, don't bother. We are going to go do spelling
> > > patches to shorten a lot of those names anyway.
> >
> > thanks.
> > I'd been wondering whether there was a guidline for this.
> > I'll relax my 80 column constraints.
>
> It's a lot more important for core kernel, and ever there, a few lines
> tend to break loose here and there.
>
> Thanks for the test code. Using your recipe, I confirmed I have the
> same controller as you. Running on a dual PIII in my case.
>
> Apparently Jens has a DAC as well. Jens, is it the same?
>
> --
> Daniel
next prev parent reply other threads:[~2002-09-23 21:57 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-23 19:04 Dave Olien
2002-09-23 19:19 ` David Mosberger
2002-09-23 20:40 ` David S. Miller
2002-09-23 20:53 ` David Mosberger
2002-09-23 20:57 ` David S. Miller
2002-09-23 21:24 ` David Mosberger
2002-09-23 21:17 ` David S. Miller
2002-09-23 21:32 ` David Mosberger
2002-09-23 21:28 ` David S. Miller
2002-09-23 21:31 ` Daniel Phillips
2002-09-23 21:33 ` David Mosberger
2002-09-23 21:28 ` David S. Miller
2002-09-23 21:40 ` Daniel Phillips
2002-09-23 21:45 ` David Mosberger
2002-09-23 20:44 ` Daniel Phillips
2002-09-23 20:54 ` David S. Miller
2002-09-24 16:54 ` Dave Olien
2002-09-24 17:11 ` David Mosberger
2002-09-24 17:28 ` Dave Olien
2002-09-24 18:21 ` David Mosberger
2002-09-24 18:25 ` Dave Olien
2002-09-24 19:12 ` David Mosberger
2002-09-24 18:45 ` Dave Olien
2002-09-24 17:50 ` Daniel Phillips
2002-09-24 18:27 ` David Mosberger
2002-09-24 17:39 ` Daniel Phillips
2002-09-25 22:20 ` DAC960, documentation links Daniel Phillips
2002-09-25 22:23 ` Daniel Phillips
2002-09-26 0:02 ` Mr. James W. Laferriere
2002-09-26 16:13 ` DAC960 in 2.5.38, with new changes Alan Cox
2002-09-24 17:45 ` Daniel Phillips
2002-09-25 21:42 ` davide.rossetti
2002-09-23 20:39 ` Daniel Phillips
2002-09-23 21:41 ` Dave Olien
2002-09-23 21:53 ` Daniel Phillips
2002-09-23 22:03 ` Dave Olien [this message]
2002-09-23 22:22 ` Daniel Phillips
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=20020923150302.A16033@acpi.pdx.osdl.net \
--to=dmo@osdl.org \
--cc=_deepfire@mail.ru \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@arcor.de \
/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
all inboxes | Powered by JetHome®