From: Greg KH <greg@kroah.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Greg KH <gregkh@suse.de>,
stable@vger.kernel.org, Konrad Rzeszutek Wilk <konrad@darnok.org>,
linux-kernel@vger.kernel.org, pjones@redhat.com
Subject: Re: [GIT PULL] ibft fix for 3.2-rc6
Date: Thu, 22 Dec 2011 12:58:37 -0800 [thread overview]
Message-ID: <20111222205837.GA30956@kroah.com> (raw)
In-Reply-To: <CAE9FiQXsnc5FqbhPaZLsFbZa1zz44M8k-9yP-ow814oPEEDhjQ@mail.gmail.com>
On Fri, Dec 16, 2011 at 04:40:34PM -0800, Yinghai Lu wrote:
> On Thu, Dec 15, 2011 at 4:37 PM, Yinghai Lu <yinghai@kernel.org> wrote:
> > On Thu, Dec 15, 2011 at 4:07 PM, Greg KH <gregkh@suse.de> wrote:
> >
> >> The patch as-is does not apply to 2.6.32, so I can't apply it there. If
> >> you want it applied there, please provide the backport to the above
> >> mentioned email address.
>
> please check back ported patch for 2.6.36 to 2.6.39
Thanks, but I don't think these kernel versions are maintained by anyone
anymore, sorry.
> We don't need to this one for 2.6.32, because EFI/ACPI ibft detecting
> is only added from 2.6.36.
>
> but 2.6.32 base kernel still could take iscsi_ibft.c related changes
> in the patch, and ignore conflicts with iscs_ibft_find.c.
> but that will add new feature to 2.6.32. Not sure if stable tree
> should take that kind of change.
No it will not, sorry.
greg k-h
prev parent reply other threads:[~2011-12-22 20:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 21:05 Konrad Rzeszutek Wilk
2011-12-15 23:15 ` Yinghai Lu
2011-12-16 0:07 ` Greg KH
2011-12-16 0:37 ` Yinghai Lu
2011-12-17 0:40 ` Yinghai Lu
2011-12-17 14:42 ` Konrad Rzeszutek Wilk
2011-12-23 0:45 ` Yinghai Lu
2011-12-23 3:50 ` Konrad Rzeszutek Wilk
2011-12-23 18:24 ` Yinghai Lu
2011-12-22 20:58 ` 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=20111222205837.GA30956@kroah.com \
--to=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=konrad@darnok.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pjones@redhat.com \
--cc=stable@vger.kernel.org \
--cc=yinghai@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
Powered by JetHome