public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Michael Karcher <karcher@physik.fu-berlin.de>
Cc: smurf@smurf.noris.de, linux-kernel@vger.kernel.org,
	linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb-serial: option: Don't match Huawei driver CD images
Date: Wed, 28 May 2008 10:17:41 -0700	[thread overview]
Message-ID: <20080528171741.GA11307@kroah.com> (raw)
In-Reply-To: <1208500241.4749.3.camel@hermes2.karcher.local>

On Fri, Apr 18, 2008 at 08:30:41AM +0200, Michael Karcher wrote:
> 
> Am Freitag, den 18.04.2008, 08:01 +0200 schrieb Michael Karcher:
> > Am Donnerstag, den 17.04.2008, 20:24 -0700 schrieb Greg KH:
> > > What is this patch against?  We have a change that went into 2.6.25
> > > after 2.6.25-rc9 that should make this patch not be needed.
> > The patch is developed against 2.6.25-rc8 + some git patches, but I have
> > forward-ported it to current git.
> > 
> > I *guess* you are talking about commit aad8a278 (USB: support more
> > Huawei data card product IDs), as I could not find .
> insert "any other patches applying to usb/usb-serial that might be
> involved" before the full stop.
> [...]
> 
> > > Can you try that release and verify this?
> > I will try with a current git kernel without my patch and report back,
> > but I will be surprised if the problem described above is gone. System
> > is currently compiling.
> Kernel compiled & booted. Won't work without the patch.

Oops, sorry, I lost this message in the queue.

Can you regenerate your patch against 2.6.26-rc4 and resend it?

thanks,

greg k-h

  reply	other threads:[~2008-05-28 17:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-17 22:49 [PATCH] usb-serial: option: Don't match Huawei driver CD images Michael Karcher
2008-04-18  3:24 ` Greg KH
2008-04-18  6:01   ` Michael Karcher
2008-04-18  6:30     ` Michael Karcher
2008-05-28 17:17       ` Greg KH [this message]
2008-05-28 21:58         ` Michael Karcher

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=20080528171741.GA11307@kroah.com \
    --to=greg@kroah.com \
    --cc=karcher@physik.fu-berlin.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=smurf@smurf.noris.de \
    /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