public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesper Juhl <jesper.juhl@gmail.com>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Kyle Moffett <mrmacman_g4@mac.com>, Paul Jackson <pj@sgi.com>,
	Jan Engelhardt <jengelh@linux01.gwdg.de>,
	linux@horizon.com, linux-kernel@vger.kernel.org,
	"linux-os (Dick Johnson)" <linux-os@analogic.com>,
	Alexey Dobriyan <adobriyan@gmail.com>
Subject: Re: kernel guide to space
Date: Sat, 23 Jul 2005 03:30:51 +0200	[thread overview]
Message-ID: <9a874849050722183040d07329@mail.gmail.com> (raw)
In-Reply-To: <9a874849050721183272f443f8@mail.gmail.com>

On 7/22/05, Jesper Juhl <jesper.juhl@gmail.com> wrote:
> On 7/21/05, Jesper Juhl <jesper.juhl@gmail.com> wrote:
> > On 7/21/05, linux-os (Dick Johnson) <linux-os@analogic.com> wrote:
> > >
> > > On Thu, 21 Jul 2005, Jesper Juhl wrote:
> > >
> > > > On 7/21/05, Kyle Moffett <mrmacman_g4@mac.com> wrote:
> > > >> On Jul 20, 2005, at 20:45:21, Paul Jackson wrote:
> > > > [...snip...]
> > > >> *cough* TargetStatistics[TargetID].HostAdapterResetsCompleted *cough*
> > > >>
> > > >> I suspect linus would be willing to accept a few cleanup patches for the
> > > >> BusLogic.c file.  Perhaps even one that renames BusLogic.c to buslogic.c
> > > >> like all the other files in the source tree, instead of using nasty
> > > >> StudlyCaps all over :-D
> > > >>
> > > >
> > > > To avoid people doing duplicate work, I just want to say that I've
> > > > started doing a CodingStyle/whitespace/VariableAndFunctionNaming
> > > > cleanup of the BusLogic driver, I'll send the patches to LKML in a few
> > > > hours.
> > > >
> > > Are you going to get rid of the BusLogic* in front of every variable
> > > and function name? (yes please??)
> > Yes, I am.
> >
> > >  If so, you will need a few days!
> >
> > That may be, it sure turned into a bigger job than I had at first
> > expected. I'll break it into a few logical bits and submit them along
> > the way. First bits in a few hours - let's see how far I get :)
> >
> >
> > > It will take probably an hour to parse:
> > > struct BusLogic_FetchHostAdapterLocalRAMReguest
> >
> > Yeah, it takes time, but I'll get it done.
> >
> Heh, it takes a little more time than I had anticipated. I've got
> ~300Kb of patches here already, and I'm only about 30% done
> (estimated).
> It makes little sense to post the patches I have at this time, since
> they don't really finish the job and leave the files in a funky
> intermediate state, so I'll hold off on posting them untill I'm a
> little closer to the goal - hopefully tomorrow I'll finish it (right
> now I need to get some sleep) - I'll post the patches as soon as I'm
> done with them...
> 
Still moving forward with this, but not yet done. I think I'm going to
need one more day to finish this.

-- 
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

  reply	other threads:[~2005-07-23  1:30 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-14  1:12 kernel guide to space linux
2005-07-20  3:41 ` Kyle Moffett
2005-07-20  7:52   ` Jan Engelhardt
2005-07-21  0:45     ` Paul Jackson
2005-07-21  6:22       ` Jan Engelhardt
2005-07-21 16:57       ` Kyle Moffett
2005-07-21 18:42         ` Jesper Juhl
2005-07-21 19:37           ` linux-os (Dick Johnson)
2005-07-21 20:11             ` Jesper Juhl
2005-07-22  1:32               ` Jesper Juhl
2005-07-23  1:30                 ` Jesper Juhl [this message]
2005-07-22  2:29             ` Miles Bader
2005-07-22  3:47               ` Paul Jackson
     [not found] <4q0yr-4YQ-3@gated-at.bofh.it>
     [not found] ` <4sdKS-7Ko-9@gated-at.bofh.it>
     [not found]   ` <4shEU-25p-5@gated-at.bofh.it>
2005-07-20 17:42     ` Bodo Eggert
     [not found] <4p851-3Tl-11@gated-at.bofh.it>
     [not found] ` <4p8HK-4he-19@gated-at.bofh.it>
     [not found]   ` <4pmUD-7gx-37@gated-at.bofh.it>
2005-07-12 19:36     ` Bodo Eggert
2005-07-13  5:46       ` Denis Vlasenko
  -- strict thread matches above, loose matches on Subject: below --
2005-07-11 14:56 Michael S. Tsirkin
2005-07-11 15:34 ` Sander
2005-07-12  6:52   ` Denis Vlasenko
2005-07-12 11:55     ` Patrick McHardy
2005-07-12 12:17       ` Richard B. Johnson
2005-07-13  6:58         ` Paul Jackson
2005-07-13 17:22           ` Lee Revell
2005-07-13 17:52             ` Paul Jackson
2005-07-13 23:38             ` Marc Singer
2005-07-11 15:44 ` Dmitry Torokhov
2005-07-11 17:19   ` Ingo Oeser
2005-07-12  7:12 ` Denis Vlasenko
2005-07-12 11:36   ` Domen Puncer
2005-07-13  7:09 ` Paul Jackson
2005-07-20 12:59 ` Jesper Juhl
2005-07-20 13:07   ` Michael S. Tsirkin
2005-07-20 21:05   ` Paul Jackson
2005-07-20 22:37   ` Krzysztof Halasa
2005-07-22 17:12     ` Patrick Draper
2005-07-22 17:51       ` Jesper Juhl
2005-07-22 19:21       ` Sam Ravnborg
2005-07-22 20:28         ` Jesper Juhl
2005-07-21  0:20   ` Horst von Brand

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=9a874849050722183040d07329@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=adobriyan@gmail.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    --cc=linux@horizon.com \
    --cc=mrmacman_g4@mac.com \
    --cc=pj@sgi.com \
    /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