On Wed, Jun 10, 2015 at 10:42 AM, Linus Walleij
wrote:
> On Fri, Jun 5, 2015 at 8:51 AM, Romain Baeriswyl
> wrote:
>
>> +Required properties:
>> +- compatible : "basic-mmio-gpio" for little endian register access or
>> + "basic-mmio-gpio-be" for big endian register access
>
> Basic
On Tue, 23 Jun 2015 17:28:50 +0530
Kishon Vijay Abraham I wrote:
> The USB2 PHY2 has a different register map compared to USB2 PHY1
> to power on/off the PHY. In order to handle it, add a new
> "compatible" string.
>
> Signed-off-by: Kishon Vijay Abraham I
> ---
> Documentation/devicetree/bind
2015-06-24 10:25 keltezéssel, Boszormenyi Zoltan írta:
> 2015-06-24 09:43 keltezéssel, Jiang Liu írta:
>> Hi Zoltan,
>> Could you please help to test this patch against the latest kernel?
>> Thanks!
>> Gerry
> I will, thanks.
Now i have tested this v2. I assume later ones will only differ in
Hi Matthias,
On Wed, Jun 24, 2015 at 4:04 AM, Matthias Brugger
wrote:
> On Monday, June 01, 2015 09:08:27 PM Eddie Huang wrote:
>> Add MT8173 I2C device nodes, include I2C controllers and pins.
>> MT8173 has six I2C controllers, from i2c0 to i2c6, exclude i2c5.
>> The 6th I2C controller register
On Sat, 13 Jun 2015, Mathias Krause wrote:
> Constify the ACPI device ID array, it doesn't need to be writable at
> runtime.
>
> Signed-off-by: Mathias Krause
> Cc: Yang, Bin
> Cc: Zhu, Lejun
> ---
> drivers/mfd/intel_soc_pmic_core.c |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
On Tue, 23 Jun 2015 17:28:49 +0530
Kishon Vijay Abraham I wrote:
> No functional change. Previously omap_control_phy_power() was used to power
> off the PHY during probe. But once phy-omap-usb2 driver is adapted to
> use syscon, omap_control_phy_power() cannot be used. Hence used
> omap_usb_power
On Tue, 19 May 2015, qipeng.zha wrote:
> From: "qipeng.zha"
Can you set your name up properly in your Git config?
> Add MFD core driver for Intel Broxton Whiskey Cove PMIC,
> which is specially accessed by hardware IPC, not a generic
> I2C device
>
> Signed-off-by: qipeng.zha
> ---
> drivers
2015-06-24 19:32 GMT+09:00 Anand Moon :
> Hi Krzysztof,
>
> On 24 June 2015 at 13:27, Krzysztof Kozlowski wrote:
>> 2015-06-24 16:16 GMT+09:00 Anand Moon :
>>> Added .shutdown function to s2mps11 to help poweroff the board succefully.
>>
>> s/succefully/successfully/
>>
>>> The device drivers set
* Nishanth Menon [150623 09:21]:
> With the recent pinctrl-single changes, SoCs such as Texas
> Instrument's OMAP processors can treat wake-up events from deeper idle
> states as interrupts.
>
> Let's add support for the optional second interrupt for wake-up using
> the generic wakeirq support ad
From: Krzysztof Kozlowski
Status of enabling suspend mode for regulator was stored in bitmap-like
long integer.
However since adding support for S2MPU02 the number of regulators
exceeded 32 so on devices with more than 32 regulators (S2MPU02 and
S2MPS13) overflow happens when shifting the bit. T
Hello Stefan,
On 15-06-24 11:56:14, Stefan Wahren wrote:
> Hi Sanchayan,
>
> Am 24.06.2015 um 07:19 schrieb maitysancha...@gmail.com:
> > On 15-06-23 21:31:41, Stefan Wahren wrote:
> >> Hi Sanchayan,
> >>
> >>> Sanchayan Maity hat am 23. Juni 2015 um 15:44
> >>> geschrieben:
> >>>
> >>>
> >>> Th
Am Mittwoch, 24. Juni 2015, 10:05:02 schrieb Ingo Molnar:
> - Once one (or two) major distros go with kdbus, it becomes a de-facto
> ABI. If the ABI is bad then that distro will hurt from it regardless of
> whether we merge it upstream or not - so technical pressure is there to
> improve it. But i
Ingo Molnar writes:
> Not because I like it so much, but because I think the merge process should
> be
> stripped of politics and emotion as much as possible: if an initial
> submission is
> good and addresses all technical review properly, and if the cost to the core
> kernel is low, then b
2015-06-24 18:31 GMT+09:00 Mark Brown :
> On Wed, Jun 24, 2015 at 01:02:28PM +0900, Krzysztof Kozlowski wrote:
>> 2015-05-28 23:44 GMT+09:00 Mark Brown :
>> > On Wed, May 27, 2015 at 12:22:08PM +0900, Krzysztof Kozlowski wrote:
>> >> Status of enabling suspend mode for regulator was stored in bitma
* Kishon Vijay Abraham I [150623 05:02]:
> --- a/arch/arm/boot/dts/omap4.dtsi
> +++ b/arch/arm/boot/dts/omap4.dtsi
> @@ -852,12 +852,6 @@
> };
> };
>
> - omap_control_usbotg: control-phy@4a00233c {
> - compatible = "ti,control-p
On Tue, 23 Jun 2015 17:28:48 +0530
Kishon Vijay Abraham I wrote:
> Deprecate using phy-omap-control driver to set PCS value of the PHY
> and start using *syscon* framework to do the same.
>
> Signed-off-by: Kishon Vijay Abraham I
> ---
> Documentation/devicetree/bindings/phy/ti-phy.txt |2
Hi Krzysztof,
On 24 June 2015 at 13:27, Krzysztof Kozlowski wrote:
> 2015-06-24 16:16 GMT+09:00 Anand Moon :
>> Added .shutdown function to s2mps11 to help poweroff the board succefully.
>
> s/succefully/successfully/
>
>> The device drivers set the register to turn off the PMIC.
>
> Driver or dr
From: Markus Elfring
Date: Wed, 24 Jun 2015 11:41:46 +0200
Return from the __einj_error_trigger() function directly after a failed
call for the request_mem_region() function according to the current Linux
coding style convention.
Drop an unnecessary initialisation for the variable "trigger_tab"
On Wed, Jun 24, 2015 at 11:43:33AM +0200, Vitaly Kuznetsov wrote:
> Peter Zijlstra writes:
> > On Tue, Jun 23, 2015 at 04:57:05PM +, KY Srinivasan wrote:
> >
> >> > diff --git a/kernel/cpu.c b/kernel/cpu.c
> >> > index 94bbe46..8f35ee6 100644
> >> > --- a/kernel/cpu.c
> >> > +++ b/kernel/cpu.c
With DAX, pfn mapping becoming more common. The patch adjusts GUP code
to cover pfn mapping for cases when we don't need struct page to
proceed.
To make it possible, let's change follow_page() code to return -EEXIST
error code if proper page table entry exists, but no corresponding
struct page. __
Hi James,
Am Mittwoch, 24. Juni 2015, 15:54:15 schrieb James Liao:
> On Mon, 2015-06-22 at 14:53 +0200, Heiko Stübner wrote:
> > Hi James,
> >
> > Am Montag, 22. Juni 2015, 11:38:37 schrieb James Liao:
> > > On Fri, 2015-06-19 at 13:36 +0200, Heiko Stuebner wrote:
> > >
> > > Some clocks such as
Man page for move_pages(2) specifies that status code for zero page is
supposed to be -EFAULT. Currently kernel return -ENOENT in this case.
follow_page() can do it for us, if we would ask for FOLL_DUMP.
Signed-off-by: Kirill A. Shutemov
Cc: Christoph Lameter
Cc: Hugh Dickins
---
mm/migrate.c
On Tue, 2015-06-23 at 23:19 +0200, Paul Osmialowski wrote:
> --- a/drivers/pinctrl/freescale/Kconfig
> +++ b/drivers/pinctrl/freescale/Kconfig
> +config PINCTRL_KINETIS
> + bool "Kinetis pinctrl driver"
> + depends on OF
> + depends on SOC_K70
> + select PINMUX
> + help
> +
* Jiang Liu wrote:
> A regression report from Boszormenyi Zoltan :
> There's a Realtek RTL8111/8168/8411 (PCI ID 10ec:8168, Subsystem ID 1565:230e)
> network chip on the mainboard. After the r8169 driver loaded, the IRQs in
> the machine went berserk. Keyboard keypressed arrived with considerabl
Am 24.06.2015 um 11:55 schrieb Enrico Weigelt, metux IT consult:
> Am 24.06.2015 um 11:19 schrieb Richard Weinberger:
>
> Hi,
>
>> Porting PREEMPT_RT is not that easy.
>> Did you ever?
>
> I know.
>
> OTOH, is backporting drivers to ancient kernels (where internal APIs
> often are _completely_
A regression report from Boszormenyi Zoltan :
There's a Realtek RTL8111/8168/8411 (PCI ID 10ec:8168, Subsystem ID 1565:230e)
network chip on the mainboard. After the r8169 driver loaded, the IRQs in
the machine went berserk. Keyboard keypressed arrived with considerable
latency and duplicated, so n
Am 01.06.2015 um 20:50 schrieb Felix Fietkau:
We support many different platforms, and sometimes it takes a
while to update the kernel on them.
Just curious: what makes these platforms so different from each other,
so it takes so much time to port to new kernel ? Are there things so
special, t
On Wed, Jun 24, 2015 at 10:53:30AM +0530, Sudip Mukherjee wrote:
> On Wed, Jun 24, 2015 at 12:15:52AM +0100, Luis de Bethencourt wrote:
> > On Wed, Jun 24, 2015 at 01:53:33AM +0300, Dan Carpenter wrote:
> > > Nope. Your patch is totally wrong (buggy). Please be more careful in
> > > the future.
>
Hi Linus,
here is my collected sack of patches for the v4.2 series. Quite a
lot of new SoC subdrivers and two new main drivers this time,
apart from that business as usual.
Please pull it in!
Yours,
Linus Walleij
The following changes since commit 5ebe6afaf0057ac3eaeb98defd5456894b446d22:
Li
Both intel_pmu_enable_bts() and intel_pmu_disable_bts() are in perf_event.h
header file, no need to have them declared again in the driver.
Signed-off-by: Alexander Shishkin
---
arch/x86/kernel/cpu/perf_event_intel_bts.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/arch/x86/kernel/cpu/p
Hi Peter and Ingo,
Here are two simple cleanups from my initial AUX/PT/BTS patchset.
Alexander Shishkin (2):
perf/x86/intel/bts: Cleanup: drop redundant declarations
perf/x86/intel: Kill off intel_pmu_needs_lbr_smpl for good
arch/x86/kernel/cpu/perf_event.h | 14 --
ar
The x86_lbr_exclusive commit (4807034248be "perf/x86: Mark Intel PT and
LBR/BTS as mutually exclusive") mistakenly moved intel_pmu_needs_lbr_smpl()
to perf_event.h, while another commit (a46a2300019 "perf: Simplify the
branch stack check") removed it in favor of needs_branch_stack().
This patch ge
On Wed, Jun 24, 2015 at 11:05:16AM +0530, Sudip Mukherjee wrote:
> On Tue, Jun 23, 2015 at 03:10:56PM +0200, Luis de Bethencourt wrote:
> > Remove explicit true/false comparations to bool variables.
> >
> > Signed-off-by: Luis de Bethencourt
> > ---
>
> > diff --git a/drivers/staging/rtl8192u/r8
On 24/06/15 01:24, Stephen Boyd wrote:
Can you assign the attributes to the device_type in the nvmem::struct
device? I don't see why these attributes need to be part of the class.
I will fix this.
>>
>>>+{
>>>+return class_register(&nvmem_class);
>>
>>I thought class was on the way out
kfree Checks for NULL poitner itself,
so no need of explicit NULL check
Signed-off-by: Maninder Singh
Reviewed-by: Rohit Thapliyal
---
drivers/block/skd_main.c |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/block/skd_main.c b/drivers/block/skd_main.c
index 1e46
From: Borislav Petkov
... and kill this:
In file included from drivers/gpu/drm/radeon/radeon_acpi.c:29:0:
include/acpi/video.h:46:13: warning: ‘acpi_video_set_dmi_backlight_type’
defined but not used [-Wunused-function]
static void acpi_video_set_dmi_backlight_type(enum acpi_backlight_ty
Remove explicit true/false comparisons to bool variables.
Signed-off-by: Luis de Bethencourt
---
drivers/staging/rtl8192u/ieee80211/ieee80211_rx.c | 4 ++--
drivers/staging/rtl8192u/ieee80211/ieee80211_softmac.c | 2 +-
drivers/staging/rtl8192u/ieee80211/ieee80211_tx.c | 4 ++--
dri
Hi Sanchayan,
Am 24.06.2015 um 07:19 schrieb maitysancha...@gmail.com:
> On 15-06-23 21:31:41, Stefan Wahren wrote:
>> Hi Sanchayan,
>>
>>> Sanchayan Maity hat am 23. Juni 2015 um 15:44
>>> geschrieben:
>>>
>>>
>>> The patch adds support for the On Chip One Time Programmable Peripheral
>>> (OCOTP
On Tue, Jun 23, 2015 at 8:06 AM, Andy Lutomirski wrote:
> 3. The sandbox model is, in my opinion, an experiment that isn't going
> to succeed. It's a poor model: a "restricted endpoint" (i.e. a
> sandboxed kdbus client) sees a view of the world defined by a limited
> policy language implemented
On 23/06/15 10:26, Pantelis Antoniou wrote:
Hi Joe,
>On Jun 23, 2015, at 05:52 , Joe Perches wrote:
>
>On Tue, 2015-06-23 at 00:08 +0100, Srinivas Kandagatla wrote:
>>This patch adds just providers part of the framework just to enable easy
>>review.
>[]
>>include/linux/nvmem-provider.h |
Am 24.06.2015 um 11:19 schrieb Richard Weinberger:
Hi,
> Porting PREEMPT_RT is not that easy.
Did you ever?
I know.
OTOH, is backporting drivers to ancient kernels (where internal APIs
often are _completely_ different) really easier ? Perhaps it might look
so, if it's just one individual dri
On 23/06/15 21:10, Stefan Wahren wrote:
Hi Srinivas,
sorry for the messed up indention.
NP,
+ */
+
+#include
+#include
+#include
+#include
+#include
+#include
+#include
+#include
+#include
+#include
Sorting alphabetically would by nice
Good Idea.
+ [...]
+/**
+ * nvmem_regis
This patch adds support of device tree to the gpio-generic driver.
Signed-off-by: Romain Baeriswyl
---
.../devicetree/bindings/gpio/gpio-generic.txt | 62
drivers/gpio/gpio-generic.c| 60 ++-
include/linux/basic_mmio_gpio.h
On Wed, 24 Jun 2015, Vitaly Kuznetsov wrote:
> Peter Zijlstra writes:
>
> > On Tue, Jun 23, 2015 at 04:57:05PM +, KY Srinivasan wrote:
> >
> >> > diff --git a/kernel/cpu.c b/kernel/cpu.c
> >> > index 94bbe46..8f35ee6 100644
> >> > --- a/kernel/cpu.c
> >> > +++ b/kernel/cpu.c
> >> > @@ -190,1
On 06/24/2015 10:44 AM, Pavel Machek wrote:
On Tue 2015-06-23 19:59:27, Stas Sergeev wrote:
02.05.2015 17:59, Pavel Machek пишет:
On Thu 2015-05-14 18:24:02, Stas Sergeev wrote:
The following sequence:
echo timer >/sys/class/leds//trigger
echo 1 >/sys/class/leds//brightness
should change the
On 23/06/15 21:28, Stefan Wahren wrote:
>@@ -26,6 +35,21 @@ void devm_nvmem_cell_put(struct device *dev, struct
>nvmem_cell *cell);
>void *nvmem_cell_read(struct nvmem_cell *cell, ssize_t *len);
>int nvmem_cell_write(struct nvmem_cell *cell, void *buf, ssize_t len);
>
>+/* direct nvmem device r
On 23/06/15 21:16, Stefan Wahren wrote:
+
>+struct device;
Do we need forward declaration of struct device_node too?
Yep, Will fix it in next version.
--srini
>+/* consumer cookie */
>[...]
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
On 23/06/15 21:35, Stefan Wahren wrote:
+Required properties:
>+reg: specifies the offset in byte within that storage device, start bit
>+ in the byte and the length in bits of the data we care about.
Is the second parameter really in bits, not bytes?
Thanks for spotting this, I will fix this
On Tue, 2015-06-23 at 15:17 -0400, Benjamin Tissoires wrote:
> drivers/input/rmi4/Kconfig | 5 +
> drivers/input/rmi4/Makefile | 2 +-
> drivers/input/rmi4/rmi_bus.c| 11 ++-
> drivers/input/rmi4/rmi_driver.h | 8
> drivers/input/rmi4/rmi_f11.c| 10
On 23/06/15 10:25, Rajendra Nayak wrote:
[]..
+Example:
+
+qfprom: qfprom@0070 {
+compatible = "qcom,qfprom";
+reg= <0x0070 0x8000>;
+...
+/* Data cells */
+tsens_calibration: calib@404 {
+reg = <0x4404 0x10>;
+
* Boszormenyi Zoltan wrote:
> 2015-06-24 10:30 keltezéssel, Ingo Molnar írta:
> > * Jiang Liu wrote:
> >
> >> Since commit 593669c2ac0f ("x86/PCI/ACPI: Use common ACPI resource
> >> interfaces to
> >> simplify implementation"), x86 PCI ACPI host bridge driver validates ACPI
> >> resources by
On 23/06/15 21:44, Stefan Wahren wrote:
Srinivas Kandagatla hat am 23. Juni 2015 um
01:09 geschrieben:
From: Maxime Ripard
Now that we have the nvmem framework, we can consolidate the common
driver code. Move the driver to the framework, and hopefully, it will
fix the sysfs file creation
On 15-06-24 10:37:43, Srinivas Kandagatla wrote:
>
>
> On 24/06/15 06:19, maitysancha...@gmail.com wrote:
> >I just tested it without the "select REGMAP_MMIO" and it works just fine.
> You just got lucky in this case, as REGMAP_MMIO is getting selected
> somewhere else.
>
> Drivers should direct
On Tue 23-06-15 14:45:17, Vlastimil Babka wrote:
> On 06/22/2015 04:18 PM, Eric B Munson wrote:
> >On Mon, 22 Jun 2015, Michal Hocko wrote:
> >
> >>On Fri 19-06-15 12:43:33, Eric B Munson wrote:
[...]
> >>>My thought on detecting was that someone might want to know if they had
> >>>a VMA that was V
On 23/06/15 20:47, Stefan Wahren wrote:
0001000
>
i want to port OCOTP driver for MXS, which hasn't MMIO. From my understanding
That's cool.
hexdump would readout the complete register range defined in provider DT node.
How can i achieve that hexdump only reads the data area within the reg
On Sun, Jun 21, 2015 at 9:52 PM, Akinobu Mita wrote:
> ctx->index_hw is zero for the CPUs which have never been onlined since
> the block queue was initialized. If one of those CPUs is hotadded and
> starts handling request before new mappings are established, pending
Could you explain a bit wha
Peter Zijlstra writes:
> On Tue, Jun 23, 2015 at 04:57:05PM +, KY Srinivasan wrote:
>
>> > diff --git a/kernel/cpu.c b/kernel/cpu.c
>> > index 94bbe46..8f35ee6 100644
>> > --- a/kernel/cpu.c
>> > +++ b/kernel/cpu.c
>> > @@ -190,17 +190,19 @@ void cpu_hotplug_done(void)
>> > void cpu_hotplug_
On 24/06/15 06:19, maitysancha...@gmail.com wrote:
I just tested it without the "select REGMAP_MMIO" and it works just fine.
You just got lucky in this case, as REGMAP_MMIO is getting selected
somewhere else.
Drivers should directly select the dependecies. In this case this driver
actually
On 24/06/15 09:35, Maxime Ripard wrote:
Hi,
On Tue, Jun 23, 2015 at 07:14:57PM +0530, Sanchayan Maity wrote:
+static struct nvmem_config ocotp_config = {
+ .name = "soc_id",
+};
+
+static struct nvmem_config rom_config = {
+ .name = "rom_rev",
+};
Srinivas, shouldn't we use the
On Wed, Jun 24, 2015 at 01:02:28PM +0900, Krzysztof Kozlowski wrote:
> 2015-05-28 23:44 GMT+09:00 Mark Brown :
> > On Wed, May 27, 2015 at 12:22:08PM +0900, Krzysztof Kozlowski wrote:
> >> Status of enabling suspend mode for regulator was stored in bitmap-like
> >> long integer.
> > Applied, thank
On Wed, Jun 24, 2015 at 10:32:57AM +0200, Peter Zijlstra wrote:
> + s = atomic_long_read(&rsp->expedited_done);
> + if (ULONG_CMP_GE((ulong)s, (ulong)snap)) {
> + /* ensure test happens before caller kfree */
> + smp_mb__before_atomic(); /* ^^^ */
FWIW isn't that gu
On Mon, Jun 22, 2015 at 11:30:30AM -0700, Juston Li wrote:
> On Mon, Jun 22, 2015 at 10:46 AM, Dan Carpenter
> wrote:
> > On Fri, Jun 19, 2015 at 05:50:50PM -0700, Juston Li wrote:
> >> void sii164ClearInterrupt(void)
> >> {
> >> -unsigned char detectReg;
> >> + unsigned char detectReg;
2015-06-24 10:30 keltezéssel, Ingo Molnar írta:
> * Jiang Liu wrote:
>
>> Since commit 593669c2ac0f ("x86/PCI/ACPI: Use common ACPI resource
>> interfaces to
>> simplify implementation"), x86 PCI ACPI host bridge driver validates ACPI
>> resources by first converting an ACPI resource to a 'stru
From: Alexey Brodkin
Date: Wed, 24 Jun 2015 11:47:41 +0300
> Current implementation of descriptor init procedure only takes
> care about setting/clearing ownership flag in "des0"/"des1"
> fields while it is perfectly possible to get unexpected bits
> set because of the following factors:
Applied
With addition of DT support to 88pm800 mfd driver, this patch
adds new DT binding documentation along with respective properties.
Signed-off-by: Vaibhav Hiremath
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/mfd/88pm800.txt | 60 +++
1 file changed, 60 insertio
As per the spec, bit 1 (INT_CLEAR_MODE) of reg addr 0xe
(page 0) controls the method of clearing interrupt
status of 88pm800 family of devices;
0: clear on read
1: clear on write
This patch allows to configure this field, through DT.
Also, as suggested by "Lee Jones" renaming DT property and
Add DT support to the 88pm800 driver, along with compatible
field for it's sub-devices (rtc, onkey and regulator)
Signed-off-by: Chao Xie
Signed-off-by: Vaibhav Hiremath
---
drivers/mfd/88pm800.c | 25 +
1 file changed, 25 insertions(+)
diff --git a/drivers/mfd/88pm800.
This patch-series adds support for Device tree to 88PM800 mfd driver.
It also enabled configuration of irq clear method through DT.
Testing::
- Boot tested on PXA1928 based platform.
- probe of mfd, rtc and regulator function passing successfully.
- Basic read operations on registers
V2 => V3
On 21.06.2015 17:14, Jonathan Cameron wrote:
I'd call this a threshold detector. The device seems to have two
comparators for each channel, one for the lower threshold, one for
the upper threshold. If the voltage level goes above the upper
threshold a FF is set, if it goes below the lower thresho
On Sun, Jun 21, 2015 at 9:52 PM, Akinobu Mita wrote:
> CPU hotplug handling for blk-mq (blk_mq_queue_reinit) updates q->mq_map
> by blk_mq_update_queue_map() for all request queues in all_q_list.
> On the other hand, q->mq_map is released and set to NULL before
> deleting the queue from all_q_list
On Wed, Jun 24, 2015 at 10:30:58AM +0200, Pavel Machek wrote:
> On Wed 2015-06-24 10:32:54, Laurentiu Palcu wrote:
> > On Sat, May 02, 2015 at 04:59:34PM +0200, Pavel Machek wrote:
> > >
> > > Should this link
> > >
> > > > More details about the chip can be found here:
> > > > http://www.ti.
Hello Linus,
could you please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git for_linus
The pull contains some small fixes and improvements in error handling for
UDF. Bundled is also one ext3 coding style fix and a fix in quota
documentation.
Top of the tree is 792
Ah. I should have read the whole thread. I sort of assumed we were
just adding abstractions for the fun of it (because I have worked in
staging for too long).
regards,
dan carpenter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@
Am 24.06.2015 um 11:09 schrieb Enrico Weigelt, metux IT consult:
> Am 29.05.2015 um 17:01 schrieb Richard Weinberger:
>
> Hi,
>
>> On Fri, May 29, 2015 at 4:53 PM, Enrico Weigelt, metux IT consult
>> wrote:
>>> Am 29.05.2015 um 04:54 schrieb Luis R. Rodriguez:
>>> Actually, I really wonder why f
On 06/24/2015 10:46 AM, Ingo Molnar wrote:
> So I'd suggest to first compare preemption behavior: does the workload
> context-switch heavily, and is it the exact same context switching rate and
> are
> the points of preemption the same as well between the two kernels?
If I read this correctly,
On Wed 24-06-15 10:27:36, Vlastimil Babka wrote:
> [add some CC's]
>
> On 06/19/2015 05:16 PM, Mark Hills wrote:
[...]
> > The system is an HP xw6600, running i686 kernel. This happens whether
How many CPUs does the machine have?
> > internal SATA HDD, SSD or external USB drive is used. I first
Am 29.05.2015 um 19:36 schrieb Theodore Ts'o:
> Yes, it's ugly, but there still are some SOC and drivers that aren't
available on newer kernels.
Why so, exactly ?
cu
--
Enrico Weigelt, metux IT consult
+49-151-27565287
MELAG Medizintechnik oHG Sitz Berlin Registergericht AG Charlottenburg HR
From: Vivien Didelot
Date: Tue, 23 Jun 2015 17:46:10 -0400
> Add support for dumping the VLAN Table Unit entries by pointing to the
> port_vlan_dump function implemented for mv88e6xxx.
>
> Signed-off-by: Vivien Didelot
There is no reason to separate this from patch #2.
--
To unsubscribe from t
Am 29.05.2015 um 17:01 schrieb Richard Weinberger:
Hi,
On Fri, May 29, 2015 at 4:53 PM, Enrico Weigelt, metux IT consult
wrote:
Am 29.05.2015 um 04:54 schrieb Luis R. Rodriguez:
Actually, I really wonder why folks are sticking to ancient kernels on
newer hardware.
Enterprise distribution ke
On Wed, Jun 24, 2015 at 4:56 PM, Viresh Kumar wrote:
> On 24-06-15, 16:44, Pi-Cheng Chen wrote:
>> One reason to put those initialization and resource allocation in probe is
>> that it's easier to handle the return value -PROBE_DEFER from clock
>> and regulator framework when trying to get clocks
FW has gained new capability where a FW client can asynchronously
notify the host that an event has occurred in its process.
The notification doesn't provide any data and host may need to query
further the FW client in order to get details of the event.
New IOCTLs are introduced for the user space
FW has gained new capability where a FW client can asynchronously
notify the host that an event has occurred in its process.
The notification doesn't provide any data and host may need to query
further the FW client in order to get details of the event.
Host can subscribe or unsubscribe to the even
On Wed, Jun 24, 2015 at 10:46:48AM +0200, Ingo Molnar wrote:
> > > > flock02
> > > > mean variance sigmamax
> > > > min
> > > > tip-111.8994 0.5874 0.766413.2022
> > > > 8.6324
> > > > t
A process can be informed about client notification also via
SIGIO with POLL_PRI event.
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/client.c | 28
drivers/misc/mei/client.h | 1 +
drivers/misc/mei/hbm.c | 7 ++-
drivers/misc/mei/main.c| 21 +
Add ioctl IOCTL_MEI_NOTIFY_SET for enabling and disabling
async event notification.
Add ioctl IOCTL_MEI_NOTIFY_GET for receiving and acking
an event notification.
Signed-off-by: Tomas Winkler
Signed-off-by: Alexander Usyskin
---
Documentation/ioctl/ioctl-number.txt | 2 ++
Documentation/misc
Polling on priority events is translated on waiting for event
notification. One need to enable notification prior for
calling select or poll system call otherwise process
will not wait.
Signed-off-by: Tomas Winkler
Signed-off-by: Alexander Usyskin
---
drivers/misc/mei/main.c | 8
1 fil
From: Alexander Usyskin
Enable drivers on mei client bus to subscribe
to asynchronous event notifications.
Introduce events_mask to the existing callback infrastructure
so it is possible to handle both RX and event notification.
Signed-off-by: Alexander Usyskin
Signed-off-by: Tomas Winkler
---
Implement sending and reception handlers for the
async event notification hbm commands.
Add client notification book keeping data required for the messages
notify_en to indicate whether notification is enabled
notify_ev to indicate whether an event is pending
Signed-off-by: Tomas Winkler
Add per client notification request infrastructure
that allows client to enable or disable async
event notification.
Signed-off-by: Tomas Winkler
Signed-off-by: Alexander Usyskin
---
drivers/misc/mei/client.c| 143 +++
drivers/misc/mei/client.h|
mei_cl_notify_get is to be called by a host client
to wait, receive, and ack the event notification.
Signed-off-by: Tomas Winkler
Signed-off-by: Alexander Usyskin
---
drivers/misc/mei/client.c | 51 ++
drivers/misc/mei/client.h | 1 +
drivers/misc/
Only FW version 2.0 and newer support the async event
notification. For backward compatibility block the feature
if the FW version is older then 2.0
Signed-off-by: Tomas Winkler
Signed-off-by: Alexander Usyskin
---
drivers/misc/mei/debugfs.c | 2 ++
drivers/misc/mei/hbm.c | 4
drivers/
On 24-06-15, 16:57, Pi-Cheng Chen wrote:
> Yes. So should it be:
> - operating-points: Refer to
> Documentation/devicetree/bindings/power/opp.txt
> for details
Right.
--
viresh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger
On Sun, Jun 21, 2015 at 9:52 PM, Akinobu Mita wrote:
> There is a race between cpu hotplug handling and adding/deleting
> gendisk for blk-mq, where both are trying to register and unregister
> the same sysfs entries.
Yes, it is one issue.
>
> cpu hotplug handling for blk-mq (blk_mq_queue_reinit)
On Wed, Jun 24, 2015 at 9:06 AM, Viresh Kumar wrote:
> Adding Mike's new email address..
>
> On 23-06-15, 23:31, Pi-Cheng Chen wrote:
>> On Mon, Jun 8, 2015 at 8:29 PM, Pi-Cheng Chen
>> wrote:
>> > This patch adds device tree binding document for MT8173 cpufreq driver.
>> >
>> > Signed-off-by: P
On 24-06-15, 16:44, Pi-Cheng Chen wrote:
> One reason to put those initialization and resource allocation in probe is
> that it's easier to handle the return value -PROBE_DEFER from clock
> and regulator framework when trying to get clocks and regulators
> consumed by cpufreq driver.
This is the s
On Wed, Jun 24, 2015 at 10:50:38AM +0200, Thomas Gleixner wrote:
> One of the solution I use for cross tree dependencies is:
>
> - Apply the commits which create a dependency to a seperate branch
>
> - Let the depending tree pull that branch
>
> - Merge the branch into the proper tip
Beata Michalska writes:
> Introduce configurable generic interface for file
> system-wide event notifications, to provide file
> systems with a common way of reporting any potential
> issues as they emerge.
>
> The notifications are to be issued through generic
> netlink interface by newly introd
On Mon 22-06-15 10:18:06, Eric B Munson wrote:
> On Mon, 22 Jun 2015, Michal Hocko wrote:
>
> > On Fri 19-06-15 12:43:33, Eric B Munson wrote:
[...]
> > > Are you objecting to the addition of the VMA flag VM_LOCKONFAULT, or the
> > > new MAP_LOCKONFAULT flag (or both)?
> >
> > I thought the MAP_
On Wed, 24 Jun 2015, Ingo Molnar wrote:
> * Borislav Petkov wrote:
>
> > > If it doesn't work or compile without the tip pile, then I'm not pulling
> > > it at
> > > all, since that means that any problems are not bisectable.
> >
> > Ok, how would you prefer this solved - should I merge the r
Current implementation of descriptor init procedure only takes
care about setting/clearing ownership flag in "des0"/"des1"
fields while it is perfectly possible to get unexpected bits
set because of the following factors:
[1] On driver probe underlying memory allocated with
dma_alloc_coheren
601 - 700 of 766 matches
Mail list logo
