From: "Boris Petkov" <petkovbb@googlemail.com>
To: "Stefan Richter" <stefanr@s5r6.in-berlin.de>
Cc: "Frans Pop" <elendil@planet.nl>,
x.guimard@free.fr, linux-kernel@vger.kernel.org,
bzolnier@gmail.com, linux-ide@vger.kernel.org
Subject: Re: Proposed patch for IDE missing commands
Date: Thu, 3 Apr 2008 17:42:32 +0200 [thread overview]
Message-ID: <9ea470500804030842ne89877dg840c960eb44f0219@mail.gmail.com> (raw)
In-Reply-To: <47F4F6D7.4050908@s5r6.in-berlin.de>
On Thu, Apr 3, 2008 at 5:25 PM, Stefan Richter
<stefanr@s5r6.in-berlin.de> wrote:
> Frans Pop wrote:
> > Boris Petkov wrote:
> >> Please, rebase/redo your patch against latest -rc kernel (in this case
> >> 2.6.25-rc8) und run it through scripts/checkpatch.pl in order to adjust it
> >> to the kernel coding style. See Documentation/CodingStyle for details.
>
> Why don't linux kernel insiders help first-time contributors here a bit
> and simply repost the patch with style fix-up? That would be a matter
> of 10 minutes or so and a more valuable contribution than a mere
> RTFCodingStyle.
Well, it'll probably take the same time to run checkpatch.pl on it and
simply do what the
tool suggests wrt to style - after all this can't be more complex than
writing kernel code
in itself, now can it? What is more, my suggestion was also to _redo_
the patch against a more
recent kernel version since ide-disk has changed since then and, even
disregarding code
style issues, the patch is inapplicable as such (e.g. deleted
functions) Finally, despite all
that who's-doing-what soul searching, redoing patches has a great
didactical value which
all of us have experienced time and again :).
--
Regards/Gruß,
Boris
next prev parent reply other threads:[~2008-04-03 15:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 6:03 Xavier
2008-04-03 9:28 ` Boris Petkov
2008-04-03 10:20 ` Frans Pop
2008-04-03 15:25 ` Stefan Richter
2008-04-03 15:42 ` Boris Petkov [this message]
2008-04-03 17:37 ` Alan Cox
2008-04-07 15:45 ` Mark Lord
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=9ea470500804030842ne89877dg840c960eb44f0219@mail.gmail.com \
--to=petkovbb@googlemail.com \
--cc=bzolnier@gmail.com \
--cc=elendil@planet.nl \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=petkovbb@gmail.com \
--cc=stefanr@s5r6.in-berlin.de \
--cc=x.guimard@free.fr \
/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®