All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Gerd Knorr <kraxel@bytesex.org>
Cc: Adrian Bunk <bunk@stusta.de>, Andrew Morton <akpm@osdl.org>,
	video4linux-list@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] bttv: make some code static
Date: Wed, 19 Jan 2005 10:20:15 +0000	[thread overview]
Message-ID: <20050119102015.GA12485@infradead.org> (raw)
In-Reply-To: <20050119094351.GA31247@bytesex>

On Wed, Jan 19, 2005 at 10:43:52AM +0100, Gerd Knorr wrote:
> > This patch was already sent on:
> > - 9 Nov 2004
> 
> Damn, yes.  I have it.  I don't consider those patches *that* important
> that I instantly forward the stuff, they'll go out with the next batch
> of v4l updates because it's less work that way.

It's usally considered a good idea to ACK a patch when you got it and
think it's okay.  


      parent reply	other threads:[~2005-01-19 10:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-19  4:57 [2.6 patch] bttv: make some code static Adrian Bunk
2005-01-19  9:43 ` Gerd Knorr
2005-01-19 10:12   ` Adrian Bunk
2005-01-19 10:20   ` Christoph Hellwig [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=20050119102015.GA12485@infradead.org \
    --to=hch@infradead.org \
    --cc=akpm@osdl.org \
    --cc=bunk@stusta.de \
    --cc=kraxel@bytesex.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=video4linux-list@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.