- Original Message -
> On Tue, Jul 01, 2014 at 10:43:13AM -0400, Jeff Layton wrote:
> > On Tue, 01 Jul 2014 06:20:10 -0700
> > Joe Perches wrote:
> >
> > > While doing a bit of adding argument names to fs.h,
> > > I looked at lm_grant and it seems the 2nd argument
> > > is always NULL.
>
clear_refs_write() has some prechecks to determine if we really walk over
a given vma. Now we have a test_walk() callback to filter vmas, so let's
utilize it.
ChangeLog v4:
- use walk_page_range instead of walk_page_vma with for loop
Signed-off-by: Naoya Horiguchi
Acked-by: Kirill A. Shutemov
-
On Tue, Jul 01, 2014 at 01:16:32PM -0400, Bob Peterson wrote:
> - Original Message -
> > On Tue, Jul 01, 2014 at 10:43:13AM -0400, Jeff Layton wrote:
> > > On Tue, 01 Jul 2014 06:20:10 -0700
> > > Joe Perches wrote:
> > >
> > > > While doing a bit of adding argument names to fs.h,
> > > >
Quoting Yadwinder Singh Brar (2014-06-29 21:01:36)
> Hi Javier,
>
> On Thu, Jun 26, 2014 at 11:45 PM, Javier Martinez Canillas
> wrote:
> > Maxim Integrated Power Management ICs are very similar with
> > regard to their clock outputs. Most of the clock drivers for
> > these chips are duplicating
Quoting Javier Martinez Canillas (2014-06-26 11:15:36)
> Like most clock drivers, the Maxim 77686 PMIC clock binding
> follows the convention that the "#clock-cells" property is
> used to specify the number of cells in a clock provider.
>
> But the binding document is not clear enough that it shal
Quoting Javier Martinez Canillas (2014-06-26 11:15:35)
> This patch adds a dt-binding include for Maxim 77686
> PMIC clock IDs that can be to be shared between the
> clk-max77686 clock driver and DeviceTree source files.
>
> Signed-off-by: Javier Martinez Canillas
> Reviewed-by: Krzysztof Kozlows
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/01/2014 10:46 AM, Naoya Horiguchi wrote:
> I triggered VM_BUG_ON() in vma_address() when I try to migrate an
> anonymous hugepage with mbind() in the kernel v3.16-rc3. This is
> because pgoff's calculation in rmap_walk_anon() fails to consider
>
Hi Hugh,
On Mon, Jun 30, 2014 at 04:55:10PM -0700, Hugh Dickins wrote:
> Hi Hannes,
>
> Your rewrite of the memcg charge/uncharge API is bold and attractive,
> but I'm having some problems with the way release_pages() now does
> uncharging in I/O completion context.
Yes, I need to make the uncha
On Tue, 1 Jul 2014 17:45:27 +0100
Russell King - ARM Linux wrote:
> Let's tell the full story rather than just presenting half of it.
>
> You indeed wanted to do what you said above, but you also wanted to
> completely change the component helpers in a way that I was not happy
> with. You wanted
On Tue, Jul 1, 2014 at 3:44 AM, Paolo Bonzini wrote:
>
> git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
I've pulled this, but I was pretty close to saying "screw this shit".
Look at commit 9a630d15f16d, and pray tell me why those kinds of
commit logs are excusable?
That commit m
On Tue, Jul 01, 2014 at 10:18:53AM +0800, Rongjun Ying wrote:
A few *really* trivial things below, otherwise this looks good:
> + if (usp->daifmt_format == SND_SOC_DAIFMT_I2S)
> + regmap_update_bits(usp->regmap, USP_RX_FRAME_CTRL,
> + USP_I2S_SYNC_CHG, USP_I2S_
Move led_mode attribute from HID device to led-class devices and rename it
msi_mode. This will also fix race condition by using attribute-groups.
Signed-off-by: Janne Kanniainen
---
Changes in v3:
- Style fixes
- Rename sysfs-class-hid-driver-gt683r to sysfs-class-leds-driver-gt6
Hi Uwe,
On Tue, 2014-07-01 at 10:23AM +0200, Uwe Kleine-König wrote:
> On Mon, Jun 30, 2014 at 09:56:33AM -0700, Soren Brinkmann wrote:
> > Introduce a new API function to find the rate a clock can provide which
> > is closest to a given rate.
> >
> > clk_round_rate() leaves it to the clock drive
> Great, I just cherry-picked and applied to my tree
> http://git.kernel.org/cgit/linux/kernel/git/cooloney/linux-leds.git/commit/?h=for-next&id=f471d9480275796dea2ac7ec249b050e70a2888d
>
> Thanks,
> -Bryan
Ok, thank you!
Janne
--
To unsubscribe from this list: send the line "unsubscribe linux-ke
On 01/07/2014 at 19:01:12 +0200, Arnd Bergmann wrote :
> On Tuesday 01 July 2014 18:48:51 Alexandre Belloni wrote:
> > On 01/07/2014 at 18:35:50 +0200, Arnd Bergmann wrote :
> > > If I read this right, disabling 'USE_OF' results in still using
> > > the old clock interface. Is that intentional? If
> Andi, can you please check that and test? If the patch is good I'll
> bump it into 3.16 with an enhanced changelog..
I think the original problem was a race, so it is not easy to reproduce.
I ran this patch in a loop over night with some stress plus
the mcelog test suite running in a loop. I c
On 07/01/14 09:32, Viresh Kumar wrote:
> Create a new routine of_clk_shared_by_cpus() that finds if clock lines are
> shared between two CPUs. This is verified by comparing "clocks" property from
> CPU's DT node.
>
> Returns 1 if clock line is shared between them, 0 if clock isn't shared and
> retu
On Tue, Jul 01, 2014 at 12:04:35AM -0500, Rob Herring wrote:
> > +- clock-names: Should contain the following:
> > + "core" Master/Core clock, have to be >= 125 MHz for SS
> > + operation and >= 60MHz for HS operation
> > +
> > +Optional clocks:
> > +
On 07/01/14 09:32, Viresh Kumar wrote:
> OPPs can be populated statically, via DT, or added at run time with
> dev_pm_opp_add().
>
> While this driver handles the first case correctly, it would fail to populate
> OPPs added at runtime. Because call to of_init_opp_table() would fail as there
> are n
From: Edward Allcutt
Date: Tue, 1 Jul 2014 09:42:14 +0100 (BST)
> If it helps any, I've been running several production machines with
> this patch for just about a year now (mostly running 3.10 stable
> series).
I guess if OpenBSD can wait more than 2 decades to implement proper
path mtu handlin
On Tue, Jul 01, 2014 at 10:46:22AM -0400, Naoya Horiguchi wrote:
> I triggered VM_BUG_ON() in vma_address() when I try to migrate an anonymous
> hugepage with mbind() in the kernel v3.16-rc3. This is because pgoff's
> calculation in rmap_walk_anon() fails to consider compound_order() only to
> have
This --strict test previously worked only for what appeared
to be cast to pointer types.
Make it work for all casts.
Also, there's no reason to show the previous line for this
type of message, so don't.
Signed-off-by: Joe Perches
---
scripts/checkpatch.pl | 6 +++---
1 file changed, 3 insertio
On 07/01/14 08:44, Masanari Iida wrote:
> This patch fix spelling typo in printk within vairous
> part of the code.
>
> Signed-off-by: Masanari Iida
Acked-by: Randy Dunlap
Thanks.
> ---
> arch/blackfin/mach-common/ints-priority.c | 2 +-
> drivers/gpu/drm/i915/intel_bios.c
On 07/01/2014 01:27 AM, Mikko Perttunen wrote:
> Inline.
>
> On 01/07/14 00:08, Stephen Warren wrote:
>> On 06/27/2014 02:11 AM, Mikko Perttunen wrote:
>>> This adds support for hardware-tracked trip points to the device tree
>>> thermal sensor framework.
>>>
>>> The framework supports an arbitrar
Hi Stephane,
Please review the followon patch I sent later. This version had some issues
as you noticed.
> > his patchkit.
> >
> It is missing NHM, WSM, Atom, mine did cover that.
True. I guess we could just use yours for that.
> > I only did Sandy Bridge and Silvermont and later so far, mostl
2014-06-30 2:05 GMT+02:00 Jingoo Han :
> On Monday, June 30, 2014 8:29 AM, Rickard Strandqvist wrote:
>>
>> Fix for possible null pointer dereferenc, and there is a risk for memory
>> leak in when something
>> unexpected happens and the function returns.
>
> Would you split the patch into two patc
On 07/01/2014 02:06 AM, Mikko Perttunen wrote:
> Inline.
>
> On 01/07/14 00:23, Stephen Warren wrote:
>> On 06/27/2014 02:11 AM, Mikko Perttunen wrote:
>>> This adds support for the Tegra SOCTHERM thermal sensing and management
>>> system found in the Tegra124 system-on-chip. This initial driver
>
On Tue, Jul 1, 2014 at 11:29 AM, John W. Linville
wrote:
> Please look in the git trees before reposting patches...
>
> commit 6437f51ec36af8ef1e3e2659439b35c37e5498e2
> Author: Kees Cook
> Date: Tue Jun 10 10:37:24 2014 -0700
>
> rtlwifi: btcoexist: avoid format string in printk
>
> Si
On Mon, Jun 30, 2014 at 3:47 PM, Bjorn Helgaas wrote:
>> Should not be dangerous, just second try.
>
> I still don't understand this. Why do we set "res->flags = 0"? That
> clears out the resource type. Where do we figure out the type of "res"
> again?
pci_bridge_check_ranges()
>> Subject: [P
On Fri, Jun 27, 2014 at 4:58 PM, H. Peter Anvin wrote:
> On 06/10/2014 10:04 PM, Yinghai Lu wrote:
>> When using kexec with 64bit kernel, bzImage and ramdisk could be
>> loaded above 4G. We need this to get correct ramdisk adress.
>>
>> Make get_ramdisk_image() global and use it for early microcod
Please look in the git trees before reposting patches...
commit 6437f51ec36af8ef1e3e2659439b35c37e5498e2
Author: Kees Cook
Date: Tue Jun 10 10:37:24 2014 -0700
rtlwifi: btcoexist: avoid format string in printk
Since CL_PRINTF only ever takes a single argument, make sure a format
Can someone give me a review for this series and the corresponding mpt3sas one?
Thanks!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read t
On Tue, Jul 01, 2014 at 01:16:11PM -0400, Johannes Weiner wrote:
> On Mon, Jun 30, 2014 at 05:47:59PM +0100, Mel Gorman wrote:
> > Changelog since V3
> > o Push down kwapd changes to cover the balance gap
> > o Drop drop page distribution patch
> >
> > Changelog since V2
> > o Simply fair zone pol
use mm.h definition
Cc: Daniel Vetter
Cc: Jani Nikula
Cc: intel-...@lists.freedesktop.org
Cc: dri-de...@lists.freedesktop.org
Signed-off-by: Fabian Frederick
---
drivers/gpu/drm/i915/intel_display.c | 10 +-
drivers/gpu/drm/i915/intel_fbdev.c | 2 +-
2 files changed, 6 insertions(+)
Am 30.06.2014 21:37, schrieb Alessandro Zummo:
On Sat, 28 Jun 2014 20:54:33 +0200
Marc Dietrich wrote:
Besides that the current hctosys-mechanism doesn't really work with
hot-plugable devices at all. Guess what N will be when you unplug and
plug in such a RTC again.
We have a patch in the ke
This patch introduces the use of devm_ioremap_resource. It does away
with call to request_mem_region and the error checking on
platform_get_resource. Also, the calls to free the allocated resources
like release_mem_region and iounmap are done away with. The ret variable
in the probe function is als
Use the generic host bridge functions to provide support for
PCI Express on arm64.
Signed-off-by: Liviu Dudau
---
arch/arm64/Kconfig| 19 -
arch/arm64/include/asm/Kbuild | 1 +
arch/arm64/include/asm/io.h | 3 ++-
arch/arm64/include/asm/pci.h | 49 +++
This is a useful function and we should make it visible outside the
generic PCI code. Export it as a GPL symbol.
Signed-off-by: Liviu Dudau
Tested-by: Tanmay Inamdar
---
drivers/pci/host-bridge.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/pci/host-bridge.c b/d
Introduce a default implementation for remapping PCI bus I/O resources
onto the CPU address space. Architectures with special needs may
provide their own version, but most should be able to use this one.
Signed-off-by: Liviu Dudau
---
drivers/pci/pci.c | 33 +
i
This patch intoduces the use of devm_ioremap, does away with the ret
variable. The calls to iounmap in the probe and remove functions and no
longer needed and hence removed.
Signed-off-by: Himangi Saraogi
Acked-by: Julia Lawall
---
drivers/mailbox/mailbox-omap1.c | 12 ++--
1 file chang
The ranges property for a host bridge controller in DT describes
the mapping between the PCI bus address and the CPU physical address.
The resources framework however expects that the IO resources start
at a pseudo "port" address 0 (zero) and have a maximum size of IO_SPACE_LIMIT.
The conversion fr
This patch introduces the use of the managed version of kzalloc and
removes the kfrees in the probe and remove functions. Also, the labels
are renamed to order them.
Signed-off-by: Himangi Saraogi
Acked-by: Julia Lawall
---
drivers/staging/iio/trigger/iio-trig-bfin-timer.c | 19
Enhance the default implementation of pcibios_add_device() to
parse and map the IRQ of the device if a DT binding is available.
Signed-off-by: Liviu Dudau
---
drivers/pci/pci.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
index 63a54a3..8e65dc3 10
Several platforms use a rather generic version of parsing
the device tree to find the host bridge ranges. Move the common code
into the generic PCI code and use it to create a pci_host_bridge
structure that can be used by arch code.
Based on early attempts by Andrew Murray to unify the code.
Used
Hi,
This patch adds support for PCI to AArch64. It is based on my v8 patch
that adds support for creating generic host bridge structure from
device tree. With that in place, I was able to boot a platform that
has PCIe host bridge support and use a PCIe network card.
Changes from v7:
- Rebased t
Some architectures do not have a simple view of the PCI I/O space
and instead use a range of CPU addresses that map to bus addresses. For
some architectures these ranges will be expressed by OF bindings
in a device tree file.
Introduce a pci_register_io_range() helper function with a generic
imple
Make it easier to discover the domain number of a bus by storing
the number in pci_host_bridge for the root bus. Several architectures
have their own way of storing this information, so it makes sense
to try to unify the code. While at this, add a new function that
creates a root bus in a given dom
On Tue, 1 Jul 2014, David Miller wrote:
If it helps any, I've been running several production machines with
this patch for just about a year now (mostly running 3.10 stable
series).
I guess if OpenBSD can wait more than 2 decades to implement proper
path mtu handling, you can wait a year to pos
On Tue, Jul 01, 2014 at 09:07:39PM +0300, Kirill A. Shutemov wrote:
> On Tue, Jul 01, 2014 at 10:46:22AM -0400, Naoya Horiguchi wrote:
> > I triggered VM_BUG_ON() in vma_address() when I try to migrate an anonymous
> > hugepage with mbind() in the kernel v3.16-rc3. This is because pgoff's
> > calcu
This is my resurected attempt at adding support for generic PCI host
bridge controllers that make use of device tree information to
configure themselves. I've tagged it as v8 although the patches
have now been reshuffled in order to ease adoption so referring to
the older versions might be a bit of
use mm.h definition
Cc: David Airlie
Cc: Tomi Valkeinen
Cc: dri-de...@lists.freedesktop.org
Signed-off-by: Fabian Frederick
---
drivers/gpu/drm/omapdrm/omap_fbdev.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/omapdrm/omap_fbdev.c
b/drivers/gpu/drm/omapd
The inline version of ioport_map() that gets used when !CONFIG_GENERIC_IOMAP
is wrong. It returns a mapped (i.e. virtual) address that can start from
zero and completely ignores the PCI_IOBASE and IO_SPACE_LIMIT that most
architectures that use !CONFIG_GENERIC_MAP define.
Signed-off-by: Liviu Duda
Before commit 7b5436635800 the pci_host_bridge was created before the root bus.
As that commit has added a needless dependency on the bus for
pci_alloc_host_bridge()
the creation order has been changed for no good reason. Revert the order of
creation as we are going to depend on the pci_host_bridg
2014-06-13 9:36 GMT-07:00 Florian Fainelli :
> It is currently possible for a generic irq chip driver to set IRQ_LEVEL
> and have its irq flow handler be handle_edge_irq. Setting IRQ_LEVEL in
> such a case does not make sense, and will actually prevent e.g: the
> software resend logic from kicking,
On Tue, Jul 1, 2014 at 1:53 PM, David Drysdale wrote:
> On Mon, Jun 30, 2014 at 01:40:40PM -0700, Andi Kleen wrote:
>> David Drysdale writes:
>>
>> > Add a new O_BENEATH_ONLY flag for openat(2) which restricts the
>> > provided path, rejecting (with -EACCES) paths that are not beneath
>> > the pr
use mm.h definition
Cc: David Airlie
Cc: David Herrmann
Cc: dri-de...@lists.freedesktop.org
Signed-off-by: Fabian Frederick
---
drivers/gpu/drm/bochs/bochs_mm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/bochs/bochs_mm.c b/drivers/gpu/drm/bochs/bochs_mm
From: Edward Allcutt
Date: Tue, 1 Jul 2014 19:50:15 +0100 (BST)
> Is there another reason you dislike this approach?
I didn't say I won't apply the patch, actually the email you are
replying to is strictly about figuring out what's happening on
the OpenBSD systems for their sake.
--
To unsubscri
Shaohua Li wrote an initial implementation of this, late last year[1].
Starting from that, I started working on some alternate implementation
choices, and ended up with something rather different.
Please take a look and let me know what you think. Patch 1 is a
design and overview doc, and patch 2
Describes the driver and its interface to make it possible for user
programs to back a LIO-exported LUN.
Signed-off-by: Andy Grover
---
Documentation/target/tcmu-design.txt | 210 +++
1 file changed, 210 insertions(+)
create mode 100644 Documentation/target/tcmu-
There's a new version of the Telewell 4G modem working with, but not
recognized by this driver.
Signed-off-by: Bernd Wachter
---
--- linux-3.15.3/drivers/net/usb/qmi_wwan.c.orig2014-07-01
21:31:07.0 +0300
+++ linux-3.15.3/drivers/net/usb/qmi_wwan.c 2014-07-01 20:39:30.0
Add a LIO storage engine that presents commands to userspace for execution.
This would allow more complex backstores to be implemented out-of-kernel,
and also make experimentation a-la FUSE (but at the SCSI level -- "SUSE"?)
possible.
It uses a mmap()able UIO device per LUN to share a command ring
From: Zhengyu He
This fixes a typo that named the read_mostly section of percpu as
readmostly. It works fine with SMP because the linker script specifies
.data..percpu..readmostly. However, UP kernel builds don't have percpu
sections defined and the non-percpu version of the section is called
dat
smp: flush any
>> pending IPI callbacks before CPU offline"), which ends up calling
>> hotplug_cfd()->flush_smp_call_function_queue()->irq_work_run(), which
>> is not from IRQ context.
>>
>> And since that already calls irq_work_run() from the hotplug path,
>> r
use mm.h definition
Cc: Ming Lei
Cc: Greg Kroah-Hartman
Signed-off-by: Fabian Frederick
---
drivers/base/firmware_class.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/base/firmware_class.c b/drivers/base/firmware_class.c
index d276e33..bfe8086 100644
--- a/driver
From: Zoltan Kiss
Date: Wed, 25 Jun 2014 21:42:51 +0100
> By defining the number of frags via "nfrags", their sizes get calculated by
> pktgen. This patch allows their offsets and sizes to be specified via
> "frag_off-len", in a comma separated list (e.g.
> "frag_off-len 0-1,500-200,5000-10,9-100
From: Joe Perches
Date: Wed, 25 Jun 2014 16:55:25 -0700
> Make the code flow a little better for 80 columns.
>
> Use a consistent style for the RX and TX rings allocation.
> Use BIT macro.
> Use a temporary unsigned int entries for (1< Remove the OOM messages as they duplicate the generic
> OOM
From: Borislav Petkov
We would want to hand down a ring on which to operate so make it an
argument.
Use the obvious mce_ring_empty() in mce_ring_get() for better
readability.
Signed-off-by: Borislav Petkov
---
arch/x86/kernel/cpu/mcheck/mce.c | 22 ++
1 file changed, 10 in
From: Borislav Petkov
Add the CE collector to the polling path which collects the correctable
errors. Collect only DRAM ECC errors for now.
Signed-off-by: Borislav Petkov
---
arch/x86/kernel/cpu/mcheck/mce.c | 84
1 file changed, 76 insertions(+), 8 del
From: Borislav Petkov
Ok,
the next version.
Main changes from the last one are that we have a ce_ring now to which
MCEs get logged in atomic context first and then, in process context,
put into the CEC, just like this is done with the mce_ring.
Also, the decay of the elements in the CEC happen
From: Borislav Petkov
A simple data structure for collecting correctable errors along with
accessors. Larger description in the code itself.
Signed-off-by: Borislav Petkov
---
drivers/ras/Kconfig | 11 ++
drivers/ras/Makefile | 3 +-
drivers/ras/ce.c | 296 +
On Tue, 2014-07-01 at 12:19 -0700, David Miller wrote:
> From: Joe Perches Date: Wed, 25 Jun 2014 16:55:25 -0700
> > Make the code flow a little better for 80 columns.
[]
> > Still depends on patch 1/22: pci-dma-compat: Add pci_zalloc_consistent
> > helper
>
> If this has a dependency on a patch
On Mon, Jun 30, 2014 at 10:49 AM, Myron Stowe wrote:
> On Tue, Jun 17, 2014 at 3:07 PM, Bjorn Helgaas wrote:
>> On Tue, Jun 17, 2014 at 1:27 PM, Myron Stowe wrote:
>>> During PCIe hot-plug initialization - pciehp_probe - data structures
>>> related to slot capabilities are set up. As part of th
On Mon, Jun 30, 2014 at 8:01 PM, Austin Schuh wrote:
> On Fri, Jun 27, 2014 at 7:24 AM, Thomas Gleixner wrote:
>> Completely untested patch below.
>
> By chance, I found this in my boot logs. I'll do some more startup
> testing tomorrow.
>
> Jun 30 19:54:40 vpc5 kernel: [0.670955] --
Namhyung, Masami,
Please look at the question below. Perhaps we discussed this before,
but I can recall nothing.
On 06/30, Oleg Nesterov wrote:
>
> Actually, I'll probably try to make the patch tomorrow. It looks simple
> enough, the main complication is CONFIG_PERF. And, to keep this patch
> si
From: Borislav Petkov
For testing purposes only.
Signed-off-by: Borislav Petkov
---
arch/x86/kernel/cpu/mcheck/mce.c | 28 +++-
drivers/ras/ce.c | 28 +++-
include/linux/ras.h | 1 +
3 files changed, 55 insertions(+)
On Tuesday 01 July 2014 19:43:28 Liviu Dudau wrote:
> +/*
> + * Record the PCI IO range (expressed as CPU physical address + size).
> + * Return a negative value if an error has occured, zero otherwise
> + */
> +int __weak pci_register_io_range(phys_addr_t addr, resource_size_t size)
> +{
> +#ifdef
On Tue, 1 Jul 2014, David Miller wrote:
I didn't say I won't apply the patch, actually the email you are
replying to is strictly about figuring out what's happening on
the OpenBSD systems for their sake.
Ah, sorry for the misunderstanding.
I'll see if I can find the place in the BSD code. Alth
use macro definition
Cc: Greg Kroah-Hartman
Cc: Josh Triplett
Cc: de...@driverdev.osuosl.org
Signed-off-by: Fabian Frederick
---
drivers/staging/lustre/lustre/libcfs/nidstrings.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/lustre/lustre/libcfs/nidst
On Mon, Jun 30 2014 at 6:30am -0400,
Paul Mackerras wrote:
> I have a machine on which 3.15 usually fails to boot, and 3.14 boots
> every time. The machine is a POWER8 2-socket server with 20 cores
> (thus 160 CPUs), 128GB of RAM, and 7 SCSI disks connected via a
> hardware-RAID-capable adapter
On Thu, 26 Jun, at 04:33:44PM, Vivek Goyal wrote:
> This patch does two thigns. It passes EFI run time mappings to second
> kernel in bootparams efi_info. Second kernel parse this info and create
> new mappings in second kernel. That means mappings in first and second
> kernel will be same. This pa
On Tue, Jul 1, 2014 at 1:01 PM, Andy Gross wrote:
> On Tue, Jul 01, 2014 at 12:04:35AM -0500, Rob Herring wrote:
>
>
>
>> > +- clock-names: Should contain the following:
>> > + "core" Master/Core clock, have to be >= 125 MHz for SS
>> > + operation and
It should be request_threaded_irq, not request_irq
Signed-off-by: Emilio López
---
kernel/irq/devres.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/irq/devres.c b/kernel/irq/devres.c
index 1ef0606..d5d0f73 100644
--- a/kernel/irq/devres.c
+++ b/kernel/irq/devres.c
@
use macro definition
Cc: Roland Dreier
Cc: Sean Hefty
Cc: linux-r...@vger.kernel.org
Signed-off-by: Fabian Frederick
---
drivers/infiniband/hw/mlx4/main.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/infiniband/hw/mlx4/main.c
b/drivers/infiniband/hw/mlx4/m
Fix checkpatch.pl warnings due to missing blank line after declarations
Signed-off-by: Matt Kurz
---
drivers/staging/wlan-ng/prism2fw.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/staging/wlan-ng/prism2fw.c
b/drivers/staging/wlan-ng/prism2fw.c
index f787035..42c14b0 100644
---
use macro definition
Cc: Eli Cohen
Cc: Roland Dreier
Cc: linux-r...@vger.kernel.org
Signed-off-by: Fabian Frederick
---
drivers/infiniband/hw/mlx5/qp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/infiniband/hw/mlx5/qp.c b/drivers/infiniband/hw/mlx5/qp.c
index d1
On Tuesday 01 July 2014 19:56:01 Alexandre Belloni wrote:
> On 01/07/2014 at 19:01:12 +0200, Arnd Bergmann wrote :
> > On Tuesday 01 July 2014 18:48:51 Alexandre Belloni wrote:
> > > On 01/07/2014 at 18:35:50 +0200, Arnd Bergmann wrote :
> > > > If I read this right, disabling 'USE_OF' results in s
fs.h is new sched.h!
Start removing unnecessary fs.h inclusions.
In the end of the whole series ~2000 useless fs.h inclusions are gone
(just need more comple testing).
Signed-off-by: Alexey Dobriyan
---
drivers/gpu/vga/vgaarb.c|1 +
drivers/input/serio/serio_raw.c
This patch introduces the use of devm_kzalloc and devm_ioremap instead
of the unmanaged interfaces. The calls to the corresponding functions to
free the allocated memory in probe and remove function are done away
with. The labels in the probe function are also removed.
Signed-off-by: Himangi Sarao
On Tue, Jul 1, 2014 at 1:05 AM, Daniel Borkmann wrote:
> On 06/28/2014 02:06 AM, Alexei Starovoitov wrote:
>>
>> Safety of eBPF programs is statically determined by the verifier, which
>> detects:
>> - loops
>> - out of range jumps
>> - unreachable instructions
>> - invalid instructions
>> - unini
On Mon, 2014-06-23 at 12:54 -0700, Markus Mayer wrote:
> I did a bit of digging on this and I am wondering if the initialization
> of "to" and "from" to 0 should instead be done in dio_get_page().
>
> The warning is caused by the return in dio_get_page():
>
> ret = dio_refill_pages(
On Tue, Jul 1, 2014 at 1:30 AM, Daniel Borkmann wrote:
> On 06/28/2014 02:06 AM, Alexei Starovoitov wrote:
>>
>> User interface:
>> cat bpf_123 > /sys/kernel/debug/tracing/__event__/filter
>>
>> where 123 is an id of the eBPF program priorly loaded.
>> __event__ is static tracepoint event.
>> (kpr
> On 29 June 2014 at 11:33 Joe Perches wrote:
>
>
> On Sun, 2014-06-29 at 11:21 +0200, Fabian Frederick wrote:
> > On Fri, 27 Jun 2014 14:37:04 -0700 Joe Perches wrote:
> []
> > > I'm not sure of the value of this as I think at some point
> > > if not already today, the compiler will optimize t
Matt suggested to change helper function names newly introduced functions
and prefix these with efi_.
Signed-off-by: Vivek Goyal
CC: Matt Fleming
CC: linux-...@vger.kernel.org
---
arch/x86/kernel/kexec-bzimage64.c |4 ++--
drivers/firmware/efi/runtime-map.c |6 +++---
include/linux/efi
Asynchronous hash API allows initiate hash calculation and perform
other tasks while hash is calculated.
This patch introduces usage of double buffering for simultaneous
hashing and reading of the next chunk of data from the storage.
Signed-off-by: Dmitry Kasatkin
---
security/integrity/ima/ima
On Tue, 1 Jul 2014 20:46:05 +0100 Matt Fleming wrote:
> > +int get_efi_runtime_map_size(void)
> > +{
> > + return nr_efi_runtime_map * efi_memdesc_size;
> > +}
> > +
> > +int get_efi_runtime_map_desc_size(void)
> > +{
> > + return efi_memdesc_size;
> > +}
> > +
> > +int efi_runtime_map_copy(v
Depending on the IMA policy, it might require to measure huge amount of files.
It may be very important to speedup hash calculation or to reduce (bettery)
energy required to do it. Currently IMA uses synchronous hash API (shash)
which is CPU based. CPU based hash calculation is very CPU intensive a
Use of multiple-page collect buffers reduces:
1) the number of block IO requests
2) the number of asynchronous hash update requests
Second is important for HW accelerated hashing, because significant
amount of time is spent for preparation of hash update operation,
which includes configuring accel
Async hash API allows to use HW acceleration for hash calculation.
It may give significant performance gain or/and reduce power consumption,
which might be very beneficial for battery powered devices.
This patch introduces hash calculation using ahash API.
ahash performance depends on data size a
On Tue, Jul 01, 2014 at 02:50:21PM -0400, Naoya Horiguchi wrote:
> On Tue, Jul 01, 2014 at 09:07:39PM +0300, Kirill A. Shutemov wrote:
> > Why do we need this special case for hugetlb page ->index? Why not use
> > PAGE_SIZE units there too? Or I miss something?
>
> hugetlb pages are never split, s
On Tue, Jul 01, 2014 at 08:50:54PM +0300, Janne Kanniainen wrote:
> -static DEVICE_ATTR_RW(leds_mode);
> +static DEVICE_ATTR_RW(mode);
> +
> +static struct attribute *gt683r_led_attrs[] = {
> + &dev_attr_mode.attr,
> + NULL
> +};
> +
> +ATTRIBUTE_GROUPS(gt683r_led);
I was referring to t
401 - 500 of 725 matches
Mail list logo
