From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Tejun Heo <tj@kernel.org>
Subject: Re: [GIT PULL] Driver core / sysfs patches for 3.16-rc1
Date: Mon, 2 Jun 2014 22:46:05 -0700 [thread overview]
Message-ID: <20140603054605.GB11565@kroah.com> (raw)
In-Reply-To: <20140603054512.GA11565@kroah.com>
On Mon, Jun 02, 2014 at 10:45:12PM -0700, Greg KH wrote:
> The following changes since commit 4b660a7f5c8099d88d1a43d8ae138965112592c7:
>
> Linux 3.15-rc6 (2014-05-22 06:42:02 +0900)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/ tags/driver-core-3.16-rc1
>
> for you to fetch changes up to cda43576afa641d83ae268cb9795ae2a549d53d9:
>
> crypto/nx/nx-842: dev_set_drvdata can no longer fail (2014-05-28 13:39:51 -0700)
>
> ----------------------------------------------------------------
> Driver core / kernfs pull request for 3.16-rc1
>
> Here is the "big" pull request for 3.16-rc1.
> Not a lot of changes here, some kernfs work, a revert of a very old
> driver core change that ended up cauing some memory leaks on driver
> probe error paths, and other minor things.
>
> As was pointed out earlier today, one commit here,
> 26fc9cd200ec839e0b3095e05ae018f27314e7aa (kernfs: move the last
> knowledge of sysfs out from kernfs) is also needed in your 3.15-final
> branch as well. If you could cherry-pick it there, it would be most
> appreciated by Andy Lutomirski to prevent a regression there.
>
> All of these have been in linux-next for a while.
>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> ----------------------------------------------------------------
> Fabian Frederick (2):
> lib/devres.c: use dev in devm_request_and_ioremap
> lib/devres.c: fix checkpatch warnings
>
> Greg Kroah-Hartman (2):
> Merge 3.15-rc3 into staging-next
Note, that merge description was wrong, I merged into driver-core-next
but fat-fingered the message when doing the commit description, sorry
about that.
greg k-h
prev parent reply other threads:[~2014-06-03 5:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 5:45 Greg KH
2014-06-03 5:46 ` 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=20140603054605.GB11565@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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 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®