mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adel Gadllah <adel.gadllah@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: Stefan Bader <stefan.bader@canonical.com>,
	linux-kernel@vger.kernel.org,
	"stable-commits@vger.kernel.org" <stable-commits@vger.kernel.org>,
	reinette chatre <reinette.chatre@intel.com>,
	"linville@tuxdriver.com" <linville@tuxdriver.com>,
	"stable@kernel.org" <stable@kernel.org>
Subject: Re: [stable] patch iwlwifi-silence-tfds_in_queue-message.patch added  to 2.6.32-stable tree
Date: Tue, 30 Mar 2010 22:48:32 +0200	[thread overview]
Message-ID: <6cf6b73e1003301348u5ed9dabap8690db5ca8a8d293@mail.gmail.com> (raw)
In-Reply-To: <20100330200842.GF1693@kroah.com>

2010/3/30 Greg KH <greg@kroah.com>:
> On Tue, Mar 30, 2010 at 09:16:02AM +0200, Stefan Bader wrote:
>> Greg KH wrote:
>> > On Mon, Mar 29, 2010 at 03:09:35PM -0700, reinette chatre wrote:
>> >> Hi,
>> >>
>> >> On Mon, 2010-03-29 at 13:41 -0700, gregkh@suse.de wrote:
>> >>> This is a note to let you know that we have just queued up the patch titled
>> >>>
>> >>>     Subject: iwlwifi: Silence tfds_in_queue message
>> >>>
>> >>> to the 2.6.32-stable tree.
>> >> [...]
>> >>
>> >> Please note that this patch is really just masking a problem introduced
>> >> by a 2.6.32 backported patch. The real fix is
>> >> https://patchwork.kernel.org/patch/86722/ which should be included in
>> >> 2.6.32.
>> >
>> > What is the git commit id for that patch?  patchwork links don't help me
>> > at all.
>>
>> There isn't one. The main problem only exists in 2.6.32.y
>> because the final hunk missed to remove the nfreed++ from
>> ouside the if.
>>
>> Introduced by backport of in 2.6.32.y
>>
>> commit a120e912eb51e347f36c71b60a1d13af74d30e83
>> Author: Stanislaw Gruszka <sgruszka@redhat.com>
>> Date:   Fri Feb 19 15:47:33 2010 -0800
>>
>>     iwlwifi: sanity check before counting number of tfds can be free
>
> So, what exactly should I be doing here for the .32 stable queue?

Apply the patch that fixes the mess (i.e the one Reinette linked to)
;), whether this patch (the one you are about to push) goes in or not
does not matter much (i.e having it won't hurt, but the fix for the
real problem should go in).

Adel

  reply	other threads:[~2010-03-30 20:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <12698953011038@site>
     [not found] ` <1269900575.2446.3425.camel@rchatre-DESK>
     [not found]   ` <20100329222404.GA10927@suse.de>
2010-03-30  7:16     ` Stefan Bader
2010-03-30 20:08       ` [stable] " Greg KH
2010-03-30 20:48         ` Adel Gadllah [this message]
2010-03-31  7:21         ` Stefan Bader

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=6cf6b73e1003301348u5ed9dabap8690db5ca8a8d293@mail.gmail.com \
    --to=adel.gadllah@gmail.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=reinette.chatre@intel.com \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@kernel.org \
    --cc=stefan.bader@canonical.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 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®