mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Krufky <mkrufky@kernellabs.com>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Greg KH <greg@kroah.com>,
	Mauro Carvalho Chehab <mchehab@redhat.com>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: 2.6.27.40 build error
Date: Tue, 8 Dec 2009 18:02:23 -0500	[thread overview]
Message-ID: <37219a840912081502v3fdf1879xdb28e867eb82884c@mail.gmail.com> (raw)
In-Reply-To: <829197380912081349q32b554acob7055431d65fc26f@mail.gmail.com>

On Tue, Dec 8, 2009 at 4:49 PM, Devin Heitmueller
<dheitmueller@kernellabs.com> wrote:
> On Tue, Dec 8, 2009 at 4:42 PM, Greg KH <greg@kroah.com> wrote:
>> It turns out that the patch below causes a build failure on the
>> 2.6.27.40 kernel.
>>
>> Michael, should I just drop it, or should I take out the line with the
>> "capture_transfer_done" in it, as that member is not in the structure in
>> this kernel version.
>>
>> thanks,
>>
>> greg k-h
>
> There were several different leaks and crash conditions addressed
> since 2.6.27, and it is entirely possible that just removing the line
> is not the correct course of action.
>
> I would propose just dropping the patch for 2.6.27, as we would have
> to rework it taking into consideration the other fixes which were done
> since then.
>
> Devin
>
> --
> Devin J. Heitmueller - Kernel Labs
> http://www.kernellabs.com

Greg,

Yes -- please drop it for now.  I didn't actually send this for
2.6.27.y anyway -- it must have gotten to you some other way.

Devin, if 2.6.27.y needs this fix, can you please generate the
appropriate backport and test it before we resubmit?

Cheers,

Mike Krufky

  parent reply	other threads:[~2009-12-08 23:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-08 21:42 Greg KH
2009-12-08 21:49 ` Devin Heitmueller
2009-12-08 23:01   ` Greg KH
2009-12-08 23:02   ` Michael Krufky [this message]
2009-12-08 23:11     ` Devin Heitmueller
2009-12-09  0:20       ` Michael Krufky

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=37219a840912081502v3fdf1879xdb28e867eb82884c@mail.gmail.com \
    --to=mkrufky@kernellabs.com \
    --cc=dheitmueller@kernellabs.com \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@redhat.com \
    --cc=stable@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

all inboxes | Powered by JetHome®