public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor•org>
To: davem@davemloft•net
Cc: gregory.v.rose@intel•com, jeffrey.t.kirsher@intel•com,
	netdev@vger•kernel.org
Subject: Please promote b1d670f10e80 to 2.6.37/stable to fix gcc mainline build
Date: Fri, 10 Dec 2010 22:18:53 +0100	[thread overview]
Message-ID: <87aakdwcle.fsf@basil.nowhere.org> (raw)


Without this patch a gcc mainline kernel build fails. This is currently only
fixed in net-next. Could the patch please be promoted to 2.6.37 and
ideally for stable too?

Thanks,

-Andi

commit b1d670f10e8078485884f0cf7e384d890909aeaa
Author: Greg Rose <gregory.v.rose@intel•com>
Date:   Tue Nov 16 19:41:36 2010 -0800

    Remove extra struct page member from the buffer info structure
    
    declaration.
    
    Reported-by: Andi Kleen <andi@firstfloor•org>
    Signed-off-by: Greg Rose <gregory.v.rose@intel•com>
    Tested-by: Emil Tantilov <emil.s.tantilov@intel•com>
    Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel•com>


-- 
ak@linux•intel.com -- Speaking for myself only.

                 reply	other threads:[~2010-12-10 21:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87aakdwcle.fsf@basil.nowhere.org \
    --to=andi@firstfloor$(echo .)org \
    --cc=davem@davemloft$(echo .)net \
    --cc=gregory.v.rose@intel$(echo .)com \
    --cc=jeffrey.t.kirsher@intel$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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