From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-ide <linux-ide@vger.kernel.org>
Subject: Re: [PATCH 4/6] IDE: Coding Style fixes to drivers/ide/pci/it8213.c
Date: Tue, 26 Feb 2008 22:25:22 +0100 [thread overview]
Message-ID: <200802262225.22653.bzolnier@gmail.com> (raw)
In-Reply-To: <47C301F4.5010409@ru.mvista.com>
On Monday 25 February 2008, Sergei Shtylyov wrote:
> Paolo Ciarrocchi wrote:
>
> > File is now error free, only a few
> > WARNING: line over 80 characters
> > are left.
>
> > Compile tested.
>
> > Signed-off-by: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
>
> Acked-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
applied
prev parent reply other threads:[~2008-02-26 22:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-24 18:18 [PATCH 4/6] IDE: Coding Style fixes to drivers/ide/pci/it8213.c Paolo Ciarrocchi
2008-02-25 17:59 ` Sergei Shtylyov
2008-02-26 21:25 ` Bartlomiej Zolnierkiewicz [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=200802262225.22653.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paolo.ciarrocchi@gmail.com \
--cc=sshtylyov@ru.mvista.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;
as well as URLs for NNTP newsgroup(s).