All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Emelyanov <xemul@openvz.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: Linux Netdev List <netdev@vger.kernel.org>,
	Brian King <brking@linux.vnet.ibm.com>
Subject: Re: [PATCH][IBMVETH]: Use single_open instead of manual manipulations.
Date: Wed, 05 Mar 2008 14:25:16 +0300	[thread overview]
Message-ID: <47CE831C.4030508@openvz.org> (raw)
In-Reply-To: <47CE80F4.60901@garzik.org>

Jeff Garzik wrote:
> Pavel Emelyanov wrote:
>> The code opening proc entry for each device makes the
>> same thing, as the single_open does, so remove the
>> unneeded code.
>>
>> Signed-off-by: Pavel Emelyanov <xemul@openvz.org>
> 
> ACK from ibmveth maintainer?
> 

There's no such in MAINTAINERS file. Git log since 2.6.22 shows
Brian King as main contributor, he is in Cc and no reply from him.

  reply	other threads:[~2008-03-05 11:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-18 10:55 [PATCH][IBMVETH]: Use single_open instead of manual manipulations Pavel Emelyanov
2008-03-05 11:16 ` Jeff Garzik
2008-03-05 11:25   ` Pavel Emelyanov [this message]
2008-03-05 14:59     ` Brian King
2008-03-13  9:52       ` Pavel Emelyanov
2008-03-26  4:36 ` Jeff Garzik

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=47CE831C.4030508@openvz.org \
    --to=xemul@openvz.org \
    --cc=brking@linux.vnet.ibm.com \
    --cc=jeff@garzik.org \
    --cc=netdev@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 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.