From: Nikolay Borisov
Python doesn't do automatic expansion of paths. In case one passes
path of the from ~/foo/bar the gdb scripts won't automatically expand
that and as a result the symbols files won't be loaded. Fix this
by explicitly expanding all paths which begin with "~"
Signed-off-by:
This reverts commit e127a73d41ac ("scripts/gdb: add a Radix Tree Parser")
The python implementation of radix-tree was merged at the same time as
the radix-tree system was heavily reworked from commit e9256efcc8e3
("radix-tree: introduce radix_tree_empty") to 3bcadd6fa6c4 ("radix-tree:
free up the
From: Omar Sandoval
Since scripts/gdb/linux/constants.py is autogenerated, this should have
been added to .gitignore when it was introduced.
Fixes: f197d75fcad1 ("scripts/gdb: provide linux constants")
Signed-off-by: Omar Sandoval
Signed-off-by: Kieran Bingham
This reverts commit 9b5580359a84 ("scripts/gdb: add documentation
example for radix tree")
The python implementation of radix tree was merged at the same time as a
refactoring of the radix tree implementation and doesn't work. The
feature is being reverted, thus we revert the documentation as
From: Omar Sandoval
Since scripts/gdb/linux/constants.py is autogenerated, this should have
been added to .gitignore when it was introduced.
Fixes: f197d75fcad1 ("scripts/gdb: provide linux constants")
Signed-off-by: Omar Sandoval
Signed-off-by: Kieran Bingham
---
This reverts commit 9b5580359a84 ("scripts/gdb: add documentation
example for radix tree")
The python implementation of radix tree was merged at the same time as a
refactoring of the radix tree implementation and doesn't work. The
feature is being reverted, thus we revert the documentation as
Hi Andrew,
Please consider this series for integration into the current rc series.
I had hoped to get this to you, with a fixed radix-tree, rather than a
reverted one. Alas, time has gone against me, and we are nearing the end
of the window - so having discussed with Jan, we felt it best to
Hi Andrew,
Please consider this series for integration into the current rc series.
I had hoped to get this to you, with a fixed radix-tree, rather than a
reverted one. Alas, time has gone against me, and we are nearing the end
of the window - so having discussed with Jan, we felt it best to
The autogenerated constants.py file was only being built on the initial
call, and if the constants.py.in file changed. As we are utilising the
CPP hooks, we can successfully use the call if_changed_dep rules to
determine when to rebuild the file based on it's inclusions.
Reported-by: Jan Kiszka
The autogenerated constants.py file was only being built on the initial
call, and if the constants.py.in file changed. As we are utilising the
CPP hooks, we can successfully use the call if_changed_dep rules to
determine when to rebuild the file based on it's inclusions.
Reported-by: Jan Kiszka
On Tue, Jun 28, 2016 at 7:06 PM, Rob Rice wrote:
>>> drivers/mailbox/Kconfig |9 +
>>> drivers/mailbox/Makefile|2 +
>>> drivers/mailbox/mailbox-pdc/Makefile|8 +
>>> drivers/mailbox/mailbox-pdc/pdc.c | 1181
>>>
On Tue, Jun 28, 2016 at 7:06 PM, Rob Rice wrote:
>>> drivers/mailbox/Kconfig |9 +
>>> drivers/mailbox/Makefile|2 +
>>> drivers/mailbox/mailbox-pdc/Makefile|8 +
>>> drivers/mailbox/mailbox-pdc/pdc.c | 1181
>>>
On Fri, 15 Apr 2016, Eric Dumazet wrote:
> > TBF is probably a bad example because it started life as a classless
> > qdisc. There was only one built-in fifo queue that was shaped. Then
> > someone made it classful and changed this behavior. To me it sounds
> > reasonable to have the default
On Fri, 15 Apr 2016, Eric Dumazet wrote:
> > TBF is probably a bad example because it started life as a classless
> > qdisc. There was only one built-in fifo queue that was shaped. Then
> > someone made it classful and changed this behavior. To me it sounds
> > reasonable to have the default
2016-06-28 Christian König :
> Am 28.06.2016 um 16:17 schrieb Gustavo Padovan:
> > 2016-06-28 Christian König :
> >
> > > Am 27.06.2016 um 21:29 schrieb Gustavo Padovan:
> > > > From: Gustavo Padovan
> > > >
>
2016-06-28 Christian König :
> Am 28.06.2016 um 16:17 schrieb Gustavo Padovan:
> > 2016-06-28 Christian König :
> >
> > > Am 27.06.2016 um 21:29 schrieb Gustavo Padovan:
> > > > From: Gustavo Padovan
> > > >
> > > > As the array of fence callbacks held by an active struct fence_array
> > > >
Hi Andi,
Am Dienstag, 28. Juni 2016, 17:45:36 schrieb andi.sh...@gmail.com:
> From: Andi Shyti
>
> Patch 32b9b1096 has introduced a generalized concept of critical
> clock. Clocks are marked with the CLK_IS_CRITICAL, enabled during
> boot and never gated.
>
> Use the
Hi Andi,
Am Dienstag, 28. Juni 2016, 17:45:36 schrieb andi.sh...@gmail.com:
> From: Andi Shyti
>
> Patch 32b9b1096 has introduced a generalized concept of critical
> clock. Clocks are marked with the CLK_IS_CRITICAL, enabled during
> boot and never gated.
>
> Use the CLK_IS_CRITICAL instead of
On my system the display doesn't come back after a dpms suspend with
X11. The display is powered off after the configured time, but to get it
powered on I need to switch to console (and back to X). It doesn't
happen on simple keyboard or mouse input. Also the brightness is on the
lowest level,
On my system the display doesn't come back after a dpms suspend with
X11. The display is powered off after the configured time, but to get it
powered on I need to switch to console (and back to X). It doesn't
happen on simple keyboard or mouse input. Also the brightness is on the
lowest level,
Hi Andi,
Am Dienstag, 28. Juni 2016, 17:45:35 schrieb andi.sh...@gmail.com:
> From: Andi Shyti
> this patchset is the first of a series and it aims to remove
> the handling of critical clock on the rockchip clock drivers.
I'm actually waiting on the second part of that to
Hi Andi,
Am Dienstag, 28. Juni 2016, 17:45:35 schrieb andi.sh...@gmail.com:
> From: Andi Shyti
> this patchset is the first of a series and it aims to remove
> the handling of critical clock on the rockchip clock drivers.
I'm actually waiting on the second part of that to land.
The series
On Fri, 24 Jun 2016, Neil Armstrong wrote:
> In order to support the Qualcomm MDM9615 SoC, add support for the
> RPM regulator entries in the qcom-rpm driver.
>
> Acked-by: Bjorn Andersson
> Signed-off-by: Neil Armstrong
> ---
>
On Fri, 24 Jun 2016, Neil Armstrong wrote:
> In order to support the Qualcomm MDM9615 PMIC, add support for the
> pm8018 in pm8921 mfd driver.
>
> Reviewed-by: Bjorn Andersson
> Signed-off-by: Neil Armstrong
> ---
>
On Fri, 24 Jun 2016, Neil Armstrong wrote:
> In order to support the Qualcomm MDM9615 SoC, add support for the
> RPM regulator entries in the qcom-rpm driver.
>
> Acked-by: Bjorn Andersson
> Signed-off-by: Neil Armstrong
> ---
> Documentation/devicetree/bindings/mfd/qcom-rpm.txt | 1 +
>
On Fri, 24 Jun 2016, Neil Armstrong wrote:
> In order to support the Qualcomm MDM9615 PMIC, add support for the
> pm8018 in pm8921 mfd driver.
>
> Reviewed-by: Bjorn Andersson
> Signed-off-by: Neil Armstrong
> ---
> drivers/mfd/pm8921-core.c | 1 +
> 1 file changed, 1 insertion(+)
For my own
On 06/24/2016 08:06 AM, Joseph Salisbury wrote:
> On 06/22/2016 12:14 PM, Greg KH wrote:
>> On Wed, Jun 22, 2016 at 11:38:43AM -0400, Joseph Salisbury wrote:
>>> Hi Rupesh,
>>>
>>> A kernel bug report was opened against Ubuntu [0]. After a kernel
>>> bisect, it was found that reverting the
On 06/24/2016 08:06 AM, Joseph Salisbury wrote:
> On 06/22/2016 12:14 PM, Greg KH wrote:
>> On Wed, Jun 22, 2016 at 11:38:43AM -0400, Joseph Salisbury wrote:
>>> Hi Rupesh,
>>>
>>> A kernel bug report was opened against Ubuntu [0]. After a kernel
>>> bisect, it was found that reverting the
On Sun, 26 Jun 2016, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sun, 26 Jun 2016 13:56:58 +0200
>
> Adjust jump targets according to the Linux coding style convention.
> Another check for the variable "status" can be omitted then at the end.
>
>
On Sun, 26 Jun 2016, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sun, 26 Jun 2016 13:56:58 +0200
>
> Adjust jump targets according to the Linux coding style convention.
> Another check for the variable "status" can be omitted then at the end.
>
> Signed-off-by: Markus Elfring
>
On Tue, 28 Jun 2016 16:51:25 +0900,
Geert Uytterhoeven wrote:
>
> Hi Sato-san,
>
> On Tue, Jun 28, 2016 at 8:36 AM, Yoshinori Sato
> wrote:
> > Signed-off-by: Yoshinori Sato
> > ---
> > .../interrupt-controller/iodata-landisk.txt
On Sun, 26 Jun 2016, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sun, 26 Jun 2016 14:30:46 +0200
>
> This issue was detected by using the Coccinelle software.
>
> Return directly if a call of the function "devm_regmap_init_i2c"
> or "regmap_write"
On Sun, 26 Jun 2016, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sun, 26 Jun 2016 14:30:46 +0200
>
> This issue was detected by using the Coccinelle software.
>
> Return directly if a call of the function "devm_regmap_init_i2c"
> or "regmap_write" failed.
>
> Delete the jump label
On Tue, 28 Jun 2016 16:51:25 +0900,
Geert Uytterhoeven wrote:
>
> Hi Sato-san,
>
> On Tue, Jun 28, 2016 at 8:36 AM, Yoshinori Sato
> wrote:
> > Signed-off-by: Yoshinori Sato
> > ---
> > .../interrupt-controller/iodata-landisk.txt| 34 ++
> > arch/sh/boot/dts/Makefile
On Sun, 26 Jun 2016, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sun, 26 Jun 2016 14:14:54 +0200
>
> The variable "ret" will be set to an appropriate value a bit later.
> Thus omit the explicit initialisation at the beginning.
>
> Signed-off-by:
On Sun, 26 Jun 2016, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sun, 26 Jun 2016 14:14:54 +0200
>
> The variable "ret" will be set to an appropriate value a bit later.
> Thus omit the explicit initialisation at the beginning.
>
> Signed-off-by: Markus Elfring
> ---
>
On Tue, Jun 28, 2016 at 7:30 PM, Neil Armstrong wrote:
> On 06/25/2016 07:50 PM, Jassi Brar wrote:
>> -#define INTR_STAT_OFS 0x0
>> -#define INTR_SET_OFS 0x8
>> -#define INTR_CLR_OFS 0x10
>> -
>> -#define MHU_LP_OFFSET 0x0
>> -#define MHU_HP_OFFSET 0x20
>> -#define
Am 28.06.2016 um 16:17 schrieb Gustavo Padovan:
2016-06-28 Christian König :
Am 27.06.2016 um 21:29 schrieb Gustavo Padovan:
From: Gustavo Padovan
As the array of fence callbacks held by an active struct fence_array
each has a
On Tue, Jun 28, 2016 at 7:30 PM, Neil Armstrong wrote:
> On 06/25/2016 07:50 PM, Jassi Brar wrote:
>> -#define INTR_STAT_OFS 0x0
>> -#define INTR_SET_OFS 0x8
>> -#define INTR_CLR_OFS 0x10
>> -
>> -#define MHU_LP_OFFSET 0x0
>> -#define MHU_HP_OFFSET 0x20
>> -#define MHU_SEC_OFFSET 0x200
>>
Am 28.06.2016 um 16:17 schrieb Gustavo Padovan:
2016-06-28 Christian König :
Am 27.06.2016 um 21:29 schrieb Gustavo Padovan:
From: Gustavo Padovan
As the array of fence callbacks held by an active struct fence_array
each has a reference to the struct fence_array, when the owner of the
On Sun, 26 Jun 2016, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sun, 26 Jun 2016 13:03:59 +0200
>
> Adjust jump targets according to the Linux coding style convention.
> Another check for the variable "status" can be omitted then at the end.
>
>
On Sun, 26 Jun 2016, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sun, 26 Jun 2016 13:40:35 +0200
>
> The platform_device_put() function was called in one case by the
> add_child() function during error handling even if the passed
> variable "pdev"
On Sun, 26 Jun 2016, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sun, 26 Jun 2016 13:03:59 +0200
>
> Adjust jump targets according to the Linux coding style convention.
> Another check for the variable "status" can be omitted then at the end.
>
> Signed-off-by: Markus Elfring
>
On Sun, 26 Jun 2016, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sun, 26 Jun 2016 13:40:35 +0200
>
> The platform_device_put() function was called in one case by the
> add_child() function during error handling even if the passed
> variable "pdev" contained a null pointer.
> Return
On Sun, 26 Jun 2016, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sun, 26 Jun 2016 12:25:36 +0200
Please use `git send-email` when sending patches to the list.
> The platform_device_put() function was called in one case by the
> add_numbered_child()
On Sun, 26 Jun 2016, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sun, 26 Jun 2016 15:25:43 +0200
>
> Several update suggestions were taken into account
> from static source code analysis.
>
> Markus Elfring (6):
> twl-core: Return directly after a
On Sun, 26 Jun 2016, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sun, 26 Jun 2016 12:25:36 +0200
Please use `git send-email` when sending patches to the list.
> The platform_device_put() function was called in one case by the
> add_numbered_child() function during error handling
On Sun, 26 Jun 2016, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sun, 26 Jun 2016 15:25:43 +0200
>
> Several update suggestions were taken into account
> from static source code analysis.
>
> Markus Elfring (6):
> twl-core: Return directly after a failed platform_device_alloc()
>
On Mon, 27 Jun 2016, Bin Gao wrote:
> This patch adds the mapping of PMIC ADC channel to thermal zone and
> USB type-C resources. This mapping is used in the pmic thermal driver
> to notify the thermal zone with the pmic adc channel alert interrupts.
> This patch also adds three new data
On Tue, Jun 28, 2016 at 01:47:59PM +0100, Colin King wrote:
> From: Colin Ian King
Please fix things so that your mail configuration matches your git
configuration, it makes things harder to review since it looks like
you've got a non-author signoff with a missing
On Mon, 27 Jun 2016, Bin Gao wrote:
> This patch adds the mapping of PMIC ADC channel to thermal zone and
> USB type-C resources. This mapping is used in the pmic thermal driver
> to notify the thermal zone with the pmic adc channel alert interrupts.
> This patch also adds three new data
On Tue, Jun 28, 2016 at 01:47:59PM +0100, Colin King wrote:
> From: Colin Ian King
Please fix things so that your mail configuration matches your git
configuration, it makes things harder to review since it looks like
you've got a non-author signoff with a missing signed off by from
someone.
On Tue, Jun 28, 2016 at 07:47:53PM +0800, Hekuang wrote:
>
>
> 在 2016/6/27 4:48, Alexei Starovoitov 写道:
> >On Sun, Jun 26, 2016 at 11:20:52AM +, He Kuang wrote:
> >> bounds check just like ubpf library does.
> >hmm. I don't think I suggested to hack bpf/core.c into separate file
> >and
On Tue, Jun 28, 2016 at 07:47:53PM +0800, Hekuang wrote:
>
>
> 在 2016/6/27 4:48, Alexei Starovoitov 写道:
> >On Sun, Jun 26, 2016 at 11:20:52AM +, He Kuang wrote:
> >> bounds check just like ubpf library does.
> >hmm. I don't think I suggested to hack bpf/core.c into separate file
> >and
Hi Dave & Folks,
Today I'm releasing WireGuard, an encrypted and authenticated
tunneling virtual interface for the kernel. It uses next-generation
cryptography and is designed to be both easy to use and simple to
implement (only ~4000 LoC, which compared to xfrm or openvpn is
spectacular),
Hi Dave & Folks,
Today I'm releasing WireGuard, an encrypted and authenticated
tunneling virtual interface for the kernel. It uses next-generation
cryptography and is designed to be both easy to use and simple to
implement (only ~4000 LoC, which compared to xfrm or openvpn is
spectacular),
On Tue, Jun 28, 2016 at 15:27:47, Bob Copeland wrote:
> linux- wirel...@vger.kernel.org; net...@vger.kernel.org; Hahn, Maital
> Subject: Re: [PATCH 2/4] mac80211/cfg: mesh: fix healing time when a
> mesh peer is disconnecting
>
> On Tue, Jun 28, 2016 at 02:13:05PM +0300, Yaniv Machani wrote:
> >
On Tue, Jun 28, 2016 at 15:27:47, Bob Copeland wrote:
> linux- wirel...@vger.kernel.org; net...@vger.kernel.org; Hahn, Maital
> Subject: Re: [PATCH 2/4] mac80211/cfg: mesh: fix healing time when a
> mesh peer is disconnecting
>
> On Tue, Jun 28, 2016 at 02:13:05PM +0300, Yaniv Machani wrote:
> >
On Tue, 28 Jun 2016 14:58:50 +0200
Dmitry Vyukov wrote:
> Hello,
>
> While running tools/testing/selftests test suite with KASAN I hit the
> following use-after-free report:
>
>
>
> ==
> BUG: KASAN:
On Tue, 28 Jun 2016 14:58:50 +0200
Dmitry Vyukov wrote:
> Hello,
>
> While running tools/testing/selftests test suite with KASAN I hit the
> following use-after-free report:
>
>
>
> ==
> BUG: KASAN: use-after-free in
On Tue, 28 Jun 2016 17:40:36 +0300, Alexander Kapshuk said:
> Seeing this is a complete rewrite of the script from the shell
> language into awk, one would not be able to apply the patches
> submitted incrementally to be able to test each change being
> introduced separately. In this respect,
On Tue, 28 Jun 2016 17:40:36 +0300, Alexander Kapshuk said:
> Seeing this is a complete rewrite of the script from the shell
> language into awk, one would not be able to apply the patches
> submitted incrementally to be able to test each change being
> introduced separately. In this respect,
From: Andi Shyti
Hi,
this patchset is the first of a series and it aims to remove
the handling of critical clock on the rockchip clock drivers.
Patch 32b9b10961860860268961d9aad0c56a73018c37 has added a
generic clock critical handling that can be used from the
drivers.
From: Andi Shyti
Hi,
this patchset is the first of a series and it aims to remove
the handling of critical clock on the rockchip clock drivers.
Patch 32b9b10961860860268961d9aad0c56a73018c37 has added a
generic clock critical handling that can be used from the
drivers.
Because I'm not expert
From: Andi Shyti
Patch 32b9b1096 has introduced a generalized concept of critical
clock. Clocks are marked with the CLK_IS_CRITICAL, enabled during
boot and never gated.
Use the CLK_IS_CRITICAL instead of declaring a local array of
critical clock enabled during boot.
CC:
From: Andi Shyti
Patch 32b9b1096 has introduced a generalized concept of critical
clock. Clocks are marked with the CLK_IS_CRITICAL, enabled during
boot and never gated.
Use the CLK_IS_CRITICAL instead of declaring a local array of
critical clock enabled during boot.
CC: Heiko Stuebner
CC:
From: Andi Shyti
because there is no need anymore to enable critical clocks in
each driver, this function is not necessary anymore.
The drivers having critical clocks use the CLK_IS_CRITICAL flag.
Signed-off-by: Andi Shyti
---
drivers/clk/rockchip/clk.c |
From: Andi Shyti
because there is no need anymore to enable critical clocks in
each driver, this function is not necessary anymore.
The drivers having critical clocks use the CLK_IS_CRITICAL flag.
Signed-off-by: Andi Shyti
---
drivers/clk/rockchip/clk.c | 14 --
On Tue, Jun 28, 2016 at 3:47 PM, wrote:
> On Tue, 28 Jun 2016 13:19:06 +0300, Alexander Kapshuk said:
>> Definition of the 'printversion()' function. The function tests whether
>> the variable that contains the version number is empty, and prints
>> the name of the
On Tue, Jun 28, 2016 at 3:47 PM, wrote:
> On Tue, 28 Jun 2016 13:19:06 +0300, Alexander Kapshuk said:
>> Definition of the 'printversion()' function. The function tests whether
>> the variable that contains the version number is empty, and prints
>> the name of the utility and its version number
Signed-off-by: Yoshinori Sato
---
Documentation/devicetree/bindings/mfd/sm501.txt | 45 +
drivers/mfd/sm501.c | 9 +
2 files changed, 54 insertions(+)
create mode 100644
Signed-off-by: Yoshinori Sato
---
Documentation/devicetree/bindings/mfd/sm501.txt | 45 +
drivers/mfd/sm501.c | 9 +
2 files changed, 54 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mfd/sm501.txt
diff --git
On Tue, 28 Jun 2016 16:49:08 +0900,
Lee Jones wrote:
>
> On Tue, 28 Jun 2016, Yoshinori Sato wrote:
>
> > This driver have configuration parameter "device" in platform_data.
> > But don't have it in devicetree.
> >
> > This patch add "device" configuration to devicetree.
>
> This is really
On Tue, 28 Jun 2016 16:49:08 +0900,
Lee Jones wrote:
>
> On Tue, 28 Jun 2016, Yoshinori Sato wrote:
>
> > This driver have configuration parameter "device" in platform_data.
> > But don't have it in devicetree.
> >
> > This patch add "device" configuration to devicetree.
>
> This is really
On Tue, Jun 28, 2016 at 12:06:22PM +0100, Will Deacon wrote:
> On Tue, Jun 21, 2016 at 12:12:36PM +0100, Suzuki K Poulose wrote:
> > +static struct attribute_group cpuregs_attr_group = {
> > + .attrs = cpuregs_attrs,
> > + .name = "identification"
> > +};
>
> This makes sense because
On Tue, Jun 28, 2016 at 12:06:22PM +0100, Will Deacon wrote:
> On Tue, Jun 21, 2016 at 12:12:36PM +0100, Suzuki K Poulose wrote:
> > +static struct attribute_group cpuregs_attr_group = {
> > + .attrs = cpuregs_attrs,
> > + .name = "identification"
> > +};
>
> This makes sense because
On Thu, Jun 09, 2016 at 03:16:30PM +0300, Nandor Han wrote:
> Having the SDMA driver use a tasklet for running the clients
> callback introduce some issues:
> - probability to have desynchronized data because of the
> race condition created since the DMA transaction status
> is retrieved
On Thu, Jun 09, 2016 at 03:16:30PM +0300, Nandor Han wrote:
> Having the SDMA driver use a tasklet for running the clients
> callback introduce some issues:
> - probability to have desynchronized data because of the
> race condition created since the DMA transaction status
> is retrieved
Added support for the bar descriptor. This type is used for FPGAs
connect to the LPC or to a non PCI bus.
The Bar descriptor could have a maximum of 6 BARs. Each of the
devices within the FPGA could be mapped to a different BAR.
The BAR descriptor is comparable to the PCI header.
Signed-off-by:
Added support for the bar descriptor. This type is used for FPGAs
connect to the LPC or to a non PCI bus.
The Bar descriptor could have a maximum of 6 BARs. Each of the
devices within the FPGA could be mapped to a different BAR.
The BAR descriptor is comparable to the PCI header.
Signed-off-by:
2016-06-28 Chris Wilson :
> On Mon, Jun 27, 2016 at 04:29:22PM -0300, Gustavo Padovan wrote:
> > From: Gustavo Padovan
> >
> > Create sync_file->fence to abstract the type of fence we are using for
> > each sync_file. If only one fence
2016-06-28 Chris Wilson :
> On Mon, Jun 27, 2016 at 04:29:22PM -0300, Gustavo Padovan wrote:
> > From: Gustavo Padovan
> >
> > Create sync_file->fence to abstract the type of fence we are using for
> > each sync_file. If only one fence is present we use a normal struct fence
> > but if there is
- Original Message -
> From: "Abhi Das"
> To: cluster-de...@redhat.com, linux-kernel@vger.kernel.org,
> linux-fsde...@vger.kernel.org
> Cc: "Abhi Das" , "Miklos Szeredi" ,
> "Jens Axboe" , "Al Viro"
>
- Original Message -
> From: "Abhi Das"
> To: cluster-de...@redhat.com, linux-kernel@vger.kernel.org,
> linux-fsde...@vger.kernel.org
> Cc: "Abhi Das" , "Miklos Szeredi" ,
> "Jens Axboe" , "Al Viro"
>
> Sent: Wednesday, May 25, 2016 10:24:45 PM
> Subject: [PATCH] fs: Do not check for
Since duplicate trigger names are supposed to cause errors at probe time
anyway this issue is unlikely to affect anyone.
Fixes commit 2e2b6a13f5f5119c36551c1ab99b85e0ad1a2105:
iio: Refuse to register triggers with duplicate names
Signed-off-by: Crestez Dan Leonard
---
Since duplicate trigger names are supposed to cause errors at probe time
anyway this issue is unlikely to affect anyone.
Fixes commit 2e2b6a13f5f5119c36551c1ab99b85e0ad1a2105:
iio: Refuse to register triggers with duplicate names
Signed-off-by: Crestez Dan Leonard
---
On 06/27/2016 10:55 PM, Joe Perches wrote:
On Mon, 2016-06-27 at 19:53 -0500, Larry Finger wrote:
On 06/25/2016 05:46 PM, Joe Perches wrote:
This debugging macro can expand to a lot of code.
Make it a function to reduce code size.
(x86-64 defconfig w/ all rtlwifi drivers and allyesconfig)
$
On 06/27/2016 10:55 PM, Joe Perches wrote:
On Mon, 2016-06-27 at 19:53 -0500, Larry Finger wrote:
On 06/25/2016 05:46 PM, Joe Perches wrote:
This debugging macro can expand to a lot of code.
Make it a function to reduce code size.
(x86-64 defconfig w/ all rtlwifi drivers and allyesconfig)
$
2016-06-28 Christian König :
> Am 27.06.2016 um 21:29 schrieb Gustavo Padovan:
> > From: Gustavo Padovan
> >
> > As the array of fence callbacks held by an active struct fence_array
> > each has a reference to the struct fence_array,
2016-06-28 Christian König :
> Am 27.06.2016 um 21:29 schrieb Gustavo Padovan:
> > From: Gustavo Padovan
> >
> > As the array of fence callbacks held by an active struct fence_array
> > each has a reference to the struct fence_array, when the owner of the
> > fence_array is freed it must
On Tue, Jun 28, 2016 at 02:21:38PM +0100, Marc Zyngier wrote:
> On 28/06/16 12:13, Mark Rutland wrote:
> > On Mon, Jun 27, 2016 at 10:54:07AM -0700, Tai Tri Nguyen wrote:
> >> On Mon, Jun 27, 2016 at 9:00 AM, Mark Rutland wrote:
> >>> On Sat, Jun 25, 2016 at 10:54:20AM
On Tue, Jun 28, 2016 at 02:21:38PM +0100, Marc Zyngier wrote:
> On 28/06/16 12:13, Mark Rutland wrote:
> > On Mon, Jun 27, 2016 at 10:54:07AM -0700, Tai Tri Nguyen wrote:
> >> On Mon, Jun 27, 2016 at 9:00 AM, Mark Rutland wrote:
> >>> On Sat, Jun 25, 2016 at 10:54:20AM -0700, Tai Tri Nguyen
Em Tue, Jun 28, 2016 at 01:23:37PM +0100, Colin King escreveu:
> From: Colin Ian King
>
> trivial fix to spelling mistake
Thanks, applied.
> Signed-off-by: Colin Ian King
> ---
> tools/lib/bpf/libbpf.c | 2 +-
> tools/lib/bpf/libbpf.h | 2
Em Tue, Jun 28, 2016 at 01:23:37PM +0100, Colin King escreveu:
> From: Colin Ian King
>
> trivial fix to spelling mistake
Thanks, applied.
> Signed-off-by: Colin Ian King
> ---
> tools/lib/bpf/libbpf.c | 2 +-
> tools/lib/bpf/libbpf.h | 2 +-
> 2 files changed, 2 insertions(+), 2
tion for perf.data on disk format
> > The doc build fails with:
> > asciidoc: FAILED: manpage document title is mandatory
> > Makefile:276: recipe for target 'perf-file-format.xml' failed
> > make[2]: *** [perf-file-format.xml] Error 1
> > make[2]: *** Waiting for unfinish
k format
> > The doc build fails with:
> > asciidoc: FAILED: manpage document title is mandatory
> > Makefile:276: recipe for target 'perf-file-format.xml' failed
> > make[2]: *** [perf-file-format.xml] Error 1
> > make[2]: *** Waiting for unfinished jobs
> Ok,
On Tue, Jun 28, 2016 at 02:13:06PM +0300, Yaniv Machani wrote:
> From: Meirav Kama
>
> There are several values in HT info elements of mesh beacon (built by the
> mac80211) that are incorrect.
Would be good to enumerate the problems here.
> To fix them:
> 1. mac80211 will check
On Tue, Jun 28, 2016 at 02:13:06PM +0300, Yaniv Machani wrote:
> From: Meirav Kama
>
> There are several values in HT info elements of mesh beacon (built by the
> mac80211) that are incorrect.
Would be good to enumerate the problems here.
> To fix them:
> 1. mac80211 will check configuration
Michael Ellerman writes:
> On Thu, 2016-06-23 at 14:37 -0500, Reza Arbab wrote:
>> On Thu, Jun 23, 2016 at 10:47:20PM +0530, Aneesh Kumar K.V wrote:
>> > Reza Arbab writes:
>> > > These functions are making direct calls to the hash table APIs,
>> >
Michael Ellerman writes:
> On Thu, 2016-06-23 at 14:37 -0500, Reza Arbab wrote:
>> On Thu, Jun 23, 2016 at 10:47:20PM +0530, Aneesh Kumar K.V wrote:
>> > Reza Arbab writes:
>> > > These functions are making direct calls to the hash table APIs,
>> > > leading to a BUG() on systems using radix.
901 - 1000 of 2104 matches
Mail list logo