From: Jesper Juhl <jesper.juhl@gmail.com>
To: "Abhay_Salunke@dell.com" <Abhay_Salunke@dell.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [RFC][patch 2.6.14-rc2] dell_rbu: Changing packet update mechanism
Date: Thu, 29 Sep 2005 04:36:39 +0200 [thread overview]
Message-ID: <9a874849050928193667653c33@mail.gmail.com> (raw)
In-Reply-To: <597A2BC19EDD3C458F841E8724E92D4B973E26@ausx3mps301.aus.amer.dell.com>
On 9/29/05, Abhay_Salunke@dell.com <Abhay_Salunke@dell.com> wrote:
>
>
> -----Original Message-----
> From: Jesper Juhl [mailto:jesper.juhl@gmail.com]
> Sent: Wednesday, September 28, 2005 7:01 PM
> To: Salunke, Abhay
> Cc: linux-kernel@vger.kernel.org; akpm@osdl.org
> Subject: Re: [RFC][patch 2.6.14-rc2] dell_rbu: Changing packet update
> mechanism
>
> On Friday 23 September 2005 21:40, Abhay Salunke wrote:
> > Please ignore earlier patches as there was error submitting it! :-(
> > patch below is good...
> >
>
> Ok, I'm being pedantic. So shoot me.
> There are a few tiny bits CodingStyle wise that could be better. No big
> deal, I'm nitpicking in the extreme here...
>
> All of this code was ran thourgh Lindent!.
Lindent is not a panacea. It also matters what
Documentation/CodingStyle spells out and what is common practice in
other parts of the kernel.
> BTW there is a new patch which might have covered your concers.
>
Got a reference/link?
--
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
next prev parent reply other threads:[~2005-09-29 2:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 2:27 [RFC][patch 2.6.14-rc2] dell_rbu: Changing packet update mechanism Abhay_Salunke
2005-09-29 2:36 ` Jesper Juhl [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-23 19:40 Abhay Salunke
2005-09-29 0:00 ` Jesper Juhl
2005-09-23 19:33 Abhay Salunke
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=9a874849050928193667653c33@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=Abhay_Salunke@dell.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@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