Guenter Roeck | 23 Oct 02:10 2014

[GIT PULL] hwmon fixes for 3.18-rc2

Hi Linus,

Please pull hwmon fixes for Linux 3.18-rc2 from signed tag:

    git:// hwmon-for-linus-v3.18-rc2


The following changes since commit f114040e3ea6e07372334ade75d1ee0775c355e1:

  Linux 3.18-rc1 (2014-10-19 18:08:38 -0700)

are available in the git repository at:

  git:// tags/hwmon-for-linus-v3.18-rc2

for you to fetch changes up to 3d5960472de0a245c56ba55e9a59b8d0f4c69cb4:

  hwmon: (menf21bmc) Include linux/err.h (2014-10-19 18:41:18 -0700)

Fix potential compile problem for menf21bmc hwmon driver

Johannes Thumshirn (1):
      hwmon: (menf21bmc) Include linux/err.h

 drivers/hwmon/menf21bmc_hwmon.c | 1 +
(Continue reading)

Gregory Fong | 23 Oct 02:09 2014

[PATCH] mm: cma: Use %pa to avoid truncating the physical address

From: Kevin Cernekee <cernekee <at>>

Signed-off-by: Kevin Cernekee <cernekee <at>>
[gregory.0xf0 <at> rebased from 3.14 and updated commit message]
Signed-off-by: Gregory Fong <gregory.0xf0 <at>>
 mm/cma.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/mm/cma.c b/mm/cma.c
index 963bc4a..154efb0 100644
--- a/mm/cma.c
+++ b/mm/cma.c
 <at>  <at>  -288,8 +288,8  <at>  <at>  int __init cma_declare_contiguous(phys_addr_t base,
 	if (ret)
 		goto err;

-	pr_info("Reserved %ld MiB at %08lx\n", (unsigned long)size / SZ_1M,
-		(unsigned long)base);
+	pr_info("Reserved %ld MiB at %pa\n", (unsigned long)size / SZ_1M,
+		&base);
 	return 0;



Masanari Iida | 23 Oct 02:06 2014

[PATCH] gpu: drm: Fix warning caused by a parameter description in drm_crtc.c

This patch fix following error while "make xmldocs"

Warning(.//drivers/gpu/drm/drm_crtc.c:778): Excess function parameter
 'mode' description in 'drm_connector_get_cmdline_mode'

Signed-off-by: Masanari Iida <standby24x7 <at>>
 drivers/gpu/drm/drm_crtc.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/drivers/gpu/drm/drm_crtc.c b/drivers/gpu/drm/drm_crtc.c
index e79c8d3..171f9a5 100644
--- a/drivers/gpu/drm/drm_crtc.c
+++ b/drivers/gpu/drm/drm_crtc.c
 <at>  <at>  -766,7 +766,6  <at>  <at>  static void drm_mode_remove(struct drm_connector *connector,
  * drm_connector_get_cmdline_mode - reads the user's cmdline mode
  *  <at> connector: connector to quwery
- *  <at> mode: returned mode
  * The kernel supports per-connector configration of its consoles through
  * use of the video= parameter. This function parses that option and


Andrea Adami | 23 Oct 01:23 2014

[PATCH] mtd: cfi_cmdset_0001.c: fix resume for LH28F640BF chips

After '#echo mem > /sys/power/state' some devices can not be properly resumed
because apparently the MTD Partition Configuration Register has been reset
to default thus the rootfs cannot be mounted cleanly on resume.
An example of this can be found in the SA-1100 Developer's Manual at
where the second step of the Sleep Shutdown Sequence is described:
"An internal reset is applied to the SA-1100. All units are reset...".

As workaround we refresh the PCR value as done initially on chip setup.

This behavior and the fix are confirmed by our tests done on 2 different Zaurus
collie units with kernel 3.17.

Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov <at>>
Signed-off-by: Andrea Adami <andrea.adami <at>>
 drivers/mtd/chips/cfi_cmdset_0001.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/mtd/chips/cfi_cmdset_0001.c b/drivers/mtd/chips/cfi_cmdset_0001.c
index a7543ba..59e2355 100644
--- a/drivers/mtd/chips/cfi_cmdset_0001.c
+++ b/drivers/mtd/chips/cfi_cmdset_0001.c
 <at>  <at>  -2590,6 +2590,8  <at>  <at>  static void cfi_intelext_resume(struct mtd_info *mtd)

 		/* Go to known state. Chip may have been power cycled */
 		if (chip->state == FL_PM_SUSPENDED) {
+			/* Refresh LH28F640BF Partition Config. Register */
+			fixup_LH28F640BF(mtd);
 			map_write(map, CMD(0xFF), cfi->chips[i].start);
 			chip->oldstate = chip->state = FL_READY;
(Continue reading)

Adecco UK | 23 Oct 01:18 2014

Jobs & Careers via Adecco UK

Dear Expatriate,

Adecco is a recruitment provider that creates the opportunity for you
to live in the UK and work with some of the most exciting companies.

Our recruitment is broad, so regardless of your education and
industry, we will have your Resume forwarded to the appropriate
companies and considered for various openings.

Send us your Resume in reply to this notice and let us help you get a
better job.


Arlo Colston
Adecco UK
w.danford | 23 Oct 01:09 2014

source file /drivers/base/platform.c

Following originally sent to  gregkh <at>
Automated reply suggested to send here and/or resend if I
desire this to specifically go to Greg.  I only wish to
point out a type of 'bug' in the file named.

---- Bug discovered, fix offered ----

in file platform.c


 * platform_get_resource - get a resource for a device
 *  <at> dev: platform device
 *  <at> type: resource type
 *  <at> num: resource index
struct resource *platform_get_resource(struct platform_device *dev,
				       unsigned int type, unsigned int num)
	int i;

	for (i = 0; i < dev->num_resources; i++) {
		struct resource *r = &dev->resource[i];

//		if (type == resource_type(r) && num-- == 0)
		if (num-- == 0 && type == resource_type(r))
			return r;
	return NULL;
(Continue reading)

Seth Forshee | 22 Oct 23:24 2014

[PATCH v5 0/4] fuse: Add support for mounts from pid/user namespaces

Here's another update to the patches to enable userns mounts in fuse.
The changes this time around center on xattrs and allow_other. I'm
considering the following patch to be a prerequisite for this series: <at>

With this patch I'm dropping the xattr restrictions from the v4 patches.
This leaves the situation with xattrs unchanged in init_user_ns. A fuse
userns mount could still supply xattrs which the user would normally be
unable to set, but since the mount will be inaccessible outside of that
userns or its descendants those xattrs will never be seen by the host.

I'm also in agreement with Andy that some decision regarding this patch
should be made before merging the fuse userns support as well: <at>

Changes since v4:
 - Drop patch to restrict xattrs
 - Update allow_other to restrict based on userns of current rather than


Seth Forshee (4):
  fuse: Add support for pid namespaces
  fuse: Support fuse filesystems outside of init_user_ns
  fuse: Restrict allow_other to the superblock's namespace or a
(Continue reading)

Rasmus Villemoes | 22 Oct 23:22 2014

[PATCH v2] staging: rtl8712: Remove redundant cast

struct firmware::data has type const u8*, as does *ppmappedfw, so the
cast to u8* is unnecessary and slightly confusing.

Signed-off-by: Rasmus Villemoes <linux <at>>
 drivers/staging/rtl8712/hal_init.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/staging/rtl8712/hal_init.c b/drivers/staging/rtl8712/hal_init.c
index 1d6ade0..83f9341 100644
--- a/drivers/staging/rtl8712/hal_init.c
+++ b/drivers/staging/rtl8712/hal_init.c
 <at>  <at>  -86,7 +86,7  <at>  <at>  static u32 rtl871x_open_fw(struct _adapter *padapter, const u8 **ppmappedfw)
 		return 0;
-	*ppmappedfw = (u8 *)((*praw)->data);
+	*ppmappedfw = (*praw)->data;
 	return (*praw)->size;



H. Peter Anvin | 22 Oct 23:11 2014

[GIT PULL] x86/efi for v3.18-rc2

Hi Linus,

This patchset falls under the "maintainers that grovel" clause in the
v3.18-rc1 announcement.  We had intended to push it late in the merge
window since we got it into the -tip tree relatively late.

Many of these are relatively simple things, but there are a couple of
key bits, especially Ard's and Matt's patches as listed below.


The following changes since commit fe82dcec644244676d55a1384c958d5f67979adb:

  Linux 3.17-rc7 (2014-09-28 14:29:07 -0700)

are available in the git repository at:

  git:// x86-efi-for-linus

for you to fetch changes up to 75b128573b275d5a5a7210b98c4b8cb3b39c12e7:

  Merge branch 'next' into efi-next-merge (2014-10-03 22:15:56 +0100)


Andre Müller (1):
      x86/efi: Adding efi_printks on memory allocationa and pci.reads

Ard Biesheuvel (2):
      efi: Implement mandatory locking for UEFI Runtime Services
(Continue reading)

Arnaldo Carvalho de Melo | 22 Oct 23:06 2014

[GIT PULL 0/1] perf/urgent fix

Hi Ingo,

	Please consider pulling,

- Arnaldo

The following changes since commit 3b10ea7f922b538ba5dcb3d979a6b6b4d07daae2:

  Merge tag 'perf-core-for-mingo' of git://
into perf/urgent (2014-10-18 09:04:02 +0200)

are available in the git repository at:

  git:// tags/perf-urgent-for-mingo

for you to fetch changes up to 9ab1f50876dbb8b962db058259be7aae920d4c25:

  perf diff: Add missing hists__init() call at tool start (2014-10-22 16:31:06 -0300)

perf/urgent fix:

* Fix 'perf diff' initialization, calling the recently added hists__init()
  function so that extra space is allocated per perf_evsel for the hists storage
  that it also uses, just like report and top.  (Kan Liang)

Signed-off-by: Arnaldo Carvalho de Melo <acme <at>>

Kan Liang (1):
(Continue reading)

Scott Branden | 22 Oct 22:57 2014

[PATCH v7 0/7] Add initial support for Broadcom Cygnus SoC

This patchset contains initial support for Broadcom's Cygnus SoC based on our
iProc architecture. Initial support is minimal and includes just the mach
platform code, clock driver, and a basic device tree configuration. Peripheral
drivers will be submitted soon, as will device tree configurations for other
Cygnus board variants.

Changes from v6:
 - Additional patch added for cleanup of other areas of mach-bcm/Kconfig
   discovered during Cygnus submission review to:
   - removed one level of menu for ARCH_BCM_MOBILE in mach-bcm-Kconfig based
     on feedback from Arnd
   - added comment sections to Kconfig to identify SoC architecture groupings

Changes from v5:
 - removed one level of menu used in mach-bcm/Kconfig
 - changed MAINTAINERS to use N: to support all files associated with iproc
   and cygnus going forward
 - updated bcm_cygnus_defconfig to remove some DEBUG options that greatly
   hamper performance

Changes from v4:
 - simple clock tree used. reworked clock driver will be submitted later
 - fixed MAINTAINERS patchset error
 - removed DEBUG_UART_8250 Kconfig.debug legacy support
 - made ARCH_BCM_IPROC a silent Kconfig option
 - removed multi_v7_defconfig as it is not needed at this time, can
   support in future patchset but does not seem optimal configs for our
   current usage.

Changes from v3:
(Continue reading)