From: Stefan Bader <stefan.bader@canonical.com>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, stable@kernel.org, lwn@lwn.net
Subject: Re: Linux 2.6.32.30
Date: Wed, 02 Mar 2011 23:17:47 +0100 [thread overview]
Message-ID: <4D6EC20B.5090007@canonical.com> (raw)
In-Reply-To: <20110302204202.GB19022@suse.de>
On 03/02/2011 09:42 PM, Greg KH wrote:
> On Wed, Mar 02, 2011 at 05:50:16PM +0100, Stefan Bader wrote:
>>> FUJITA Tomonori (1):
>>> swiotlb: fix wrong panic
>>>
>>
>> This one breaks compilation of 64bit for me as swiotlb_tbl_unmap_single() does
>> not exist. It does not look like it is a simple single patch that would get it
>> back to 2.6.32.
>
> I don't understand. Is this patch somehow broken? Is there an
> additional patch I need to apply to fix the build issue? I need more
> information here.
>
This is a patch included in your 2.6.32.30 release and it is broken because it
uses a function that does not exist in 2.6.32. When I looked at the git blame of
the function in Linus tree it consists of multiple shas. So it would be more
than one single patch needed from there.
-Stefan
> thanks,
>
> greg k-h
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2011-03-02 22:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 14:58 Linux 2.6.32.30 Greg KH
2011-03-02 15:00 ` Greg KH
2011-03-02 16:50 ` Stefan Bader
2011-03-02 20:42 ` Greg KH
2011-03-02 22:17 ` Stefan Bader [this message]
2011-03-02 22:24 ` Shawn Bohrer
2011-03-02 22:29 ` David Engel
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=4D6EC20B.5090007@canonical.com \
--to=stefan.bader@canonical.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.