From: joe@perches.com (Joe Perches)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] device: Add kernel standard devm_k.alloc functions
Date: Sun, 20 Oct 2013 08:22:46 -0700 [thread overview]
Message-ID: <1382282566.2041.39.camel@joe-AO722> (raw)
In-Reply-To: <20131020025713.GA22344@kroah.com>
On Sat, 2013-10-19 at 19:57 -0700, Greg KH wrote:
> On Fri, Oct 18, 2013 at 10:52:46PM -0700, Kevin Hilman wrote:
> > Greg KH <gregkh@linuxfoundation.org> writes:
> >
> > > On Fri, Oct 18, 2013 at 10:04:11AM -0700, Kevin Hilman wrote:
> > >> > A handful of boot panics on ARM platforms were bisected to point at
> > >> > the version of this commit that's in linux-next (commit
> > >> > 64c862a839a8db2c02bbaa88b923d13e1208919d). Reverting this commit
> > >> > makes things happy again.
> > >> >
> > >> > Upon further digging, it seems that users of devres_alloc() are
> > >> > relying on the previous behavior of having the memory zero'd which is
> > >> > no longer the case after $SUBJECT patch. The change below on top of
> > >> > -next makes these ARM boards happy again.
> > >>
> > >> Oops, it should've fixed __devres_alloc() also. Updated patch below.
> > >
> > > Can you send this in a format that I can apply it in? It was whitespace
> > > damaged.
> >
> > hmm, sorry about that. This one should work, though I wonder if Andrew
> > should pick this up since I think the patch that causes the breakage
> > came through his tree.
>
> No, the patch is in my tree, not Andrew's.
>
> Joe, can I get a signed-off-by for this?
If you want.
Signed-off-by: Joe Perches <joe@perches.com>
next prev parent reply other threads:[~2013-10-20 15:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1381296747.2040.17.camel@joe-AO722>
[not found] ` <20131011131138.3bc5b2acf60df3a5d79d0d24@linux-foundation.org>
2013-10-18 16:57 ` [RFC PATCH] device: Add kernel standard devm_k.alloc functions Kevin Hilman
2013-10-18 17:04 ` Kevin Hilman
2013-10-18 22:57 ` Greg KH
2013-10-19 5:52 ` Kevin Hilman
2013-10-20 2:57 ` Greg KH
2013-10-20 15:22 ` Joe Perches [this message]
2013-10-25 12:59 ` Olof Johansson
2013-10-25 15:23 ` Greg KH
2013-10-18 17:06 ` Joe Perches
2013-10-18 17:11 ` Kevin Hilman
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=1382282566.2041.39.camel@joe-AO722 \
--to=joe@perches.com \
--cc=linux-arm-kernel@lists.infradead.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