All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: bart.hartgers@gmail.com, Mike McCormack <mikem@ring3k.org>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] ark3116: (3rd try) driver rework
Date: Sun, 25 Oct 2009 10:53:59 -0700	[thread overview]
Message-ID: <20091025175359.GA30903@suse.de> (raw)
In-Reply-To: <20091025175057.270011110@gmail.com>

On Sun, Oct 25, 2009 at 06:50:57PM +0100, bart.hartgers@gmail.com wrote:
> Hi Greg,
> 
> Third try in getting my patches to the list. Somehow send to myself
> worked, but vger seems to choke on something.

Yeah!  Third time was a charm, thanks for resending.

So, how do I resolve this, whose patch series should I take, yours or
Mike's?

You two care to work this out?

thanks,

greg k-h

      parent reply	other threads:[~2009-10-25 17:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-25 17:50 [PATCH 0/7] ark3116: (3rd try) driver rework bart.hartgers
2009-10-25 17:50 ` [PATCH 1/7] ark3116: (3rd try) Setup some basic infrastructure for new ark3116 driver bart.hartgers
2009-10-27 17:46   ` Greg KH
2009-10-27 21:35     ` Bart Hartgers
2009-10-27 22:11       ` Greg KH
2009-10-25 17:50 ` [PATCH 2/7] ark3116: (3rd try) Make existing functions 16450-aware and add close and release functions bart.hartgers
2009-10-25 19:56   ` Oliver Neukum
2009-10-25 17:51 ` [PATCH 3/7] ark3116: (3rd try) Replace cmget bart.hartgers
2009-10-25 19:52   ` Oliver Neukum
2009-10-25 19:56     ` Bart Hartgers
2009-10-25 22:08       ` Oliver Neukum
2009-10-25 17:51 ` [PATCH 4/7] ark3116: (3rd try) Add atomic set-and-clear function bart.hartgers
2009-10-25 17:51 ` [PATCH 5/7] ark3116: (3rd try) Add cmset and break bart.hartgers
2009-10-25 17:51 ` [PATCH 6/7] ark3116: (3rd try) Callbacks for interrupt and bulk read bart.hartgers
2009-10-25 17:51 ` [PATCH 7/7] ark3116: (3rd try) Cleanup of now unneeded functions bart.hartgers
2009-10-25 17:53 ` 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=20091025175359.GA30903@suse.de \
    --to=gregkh@suse.de \
    --cc=bart.hartgers@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mikem@ring3k.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.