From: Greg KH <greg@kroah.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Alexander Beregalov <a.beregalov@gmail.com>,
gregkh@suse.de, linux-kernel@vger.kernel.org,
Forest Bond <forest@alittletooquiet.net>
Subject: Re: [PATCH] Staging: vt6655: s/VOID/void/
Date: Thu, 2 Jul 2009 12:50:11 -0700 [thread overview]
Message-ID: <20090702195011.GG10957@kroah.com> (raw)
In-Reply-To: <200907021946.08452.bzolnier@gmail.com>
On Thu, Jul 02, 2009 at 07:46:08PM +0200, Bartlomiej Zolnierkiewicz wrote:
> On Saturday 20 June 2009 20:02:37 Alexander Beregalov wrote:
> > Cc: Forest Bond <forest@alittletooquiet.net>
> > Signed-off-by: Alexander Beregalov <a.beregalov@gmail.com>
>
> Looks OK but (in the light of possible vt665{5,6} unification) it should be
> also done for vt6656, or alternatively (which is what I would personally
> prefer) delayed till more complete removal of ttype.h typedefs from vt665x.
I agree, it should be done for both drivers now that they are in
linux-next.
thanks,
greg k-h
prev parent reply other threads:[~2009-07-02 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-20 18:02 [PATCH] Staging: vt6655: s/VOID/void/ Alexander Beregalov
2009-07-02 17:46 ` Bartlomiej Zolnierkiewicz
2009-07-02 19:50 ` Greg KH [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=20090702195011.GG10957@kroah.com \
--to=greg@kroah.com \
--cc=a.beregalov@gmail.com \
--cc=bzolnier@gmail.com \
--cc=forest@alittletooquiet.net \
--cc=gregkh@suse.de \
--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