On Tue, Jul 26, 2016 at 01:37:07PM -0700, Kees Cook wrote:
> These ifdefs aren't needed if we added a no-op __PAGE_OFFSET_BASE to
> the 32-bit page table headers. Then the compiler will DTRT with the
> start calculation. When CONFIG_RANDOMIZE_MEMORY is set, start will
> have a non-zero value, and
On Tue, Jul 26, 2016 at 01:37:07PM -0700, Kees Cook wrote:
> These ifdefs aren't needed if we added a no-op __PAGE_OFFSET_BASE to
> the 32-bit page table headers. Then the compiler will DTRT with the
> start calculation. When CONFIG_RANDOMIZE_MEMORY is set, start will
> have a non-zero value, and
On Tue, Jul 26, 2016 at 02:17:29PM -0700, Thomas Garnier wrote:
> I am sorry, there has been parallel work between KASLR memory
> randomization and hibernation support. That's why hibernation was not
> tested, it was not supported when the feature was created.
> Communication will be better next
On Tue, Jul 26, 2016 at 02:17:29PM -0700, Thomas Garnier wrote:
> I am sorry, there has been parallel work between KASLR memory
> randomization and hibernation support. That's why hibernation was not
> tested, it was not supported when the feature was created.
> Communication will be better next
On 07/26/2016 10:28 PM, Moore, Robert wrote:
/* Put the new state at the head of the walk list */
if (Thread)
{
AcpiDsPushWalkState (WalkState, Thread);
}
Is there any chance that Thread could be zero?
I'm not sure if this question was for me or not, but that
On 07/26/2016 10:28 PM, Moore, Robert wrote:
/* Put the new state at the head of the walk list */
if (Thread)
{
AcpiDsPushWalkState (WalkState, Thread);
}
Is there any chance that Thread could be zero?
I'm not sure if this question was for me or not, but that
Rob Clark writes:
> On Tue, Jul 26, 2016 at 7:11 PM, Eric Anholt wrote:
>> Rob Clark writes:
>>
>>> On Tue, Jul 26, 2016 at 4:47 PM, Eric Anholt wrote:
Overflow memory handling is tricky: While it's still
Rob Clark writes:
> On Tue, Jul 26, 2016 at 7:11 PM, Eric Anholt wrote:
>> Rob Clark writes:
>>
>>> On Tue, Jul 26, 2016 at 4:47 PM, Eric Anholt wrote:
Overflow memory handling is tricky: While it's still referenced by the
BPO registers, we want to keep it from being freed. When we
At the hardware level, the J-Core PIT is integrated with the interrupt
controller, but it is represented as its own device and has an
independent programming interface. It provides a 12-bit countdown
timer, which is not presently used, and a periodic timer. The interval
length for the latter is
At the hardware level, the J-Core PIT is integrated with the interrupt
controller, but it is represented as its own device and has an
independent programming interface. It provides a 12-bit countdown
timer, which is not presently used, and a periodic timer. The interval
length for the latter is
This driver is used with the J2, an open-source VHDL reimplementation
of SH-2.
I've split this out from the main J-Core support patches going
upstream through my own linux-sh tree. Changes since the v3 are mainly
cleanup/simplification, inclusion of sched_clock support based on
suggestions by
Signed-off-by: Rich Felker
---
.../devicetree/bindings/timer/jcore,pit.txt| 25 ++
1 file changed, 25 insertions(+)
create mode 100644 Documentation/devicetree/bindings/timer/jcore,pit.txt
diff --git
This driver is used with the J2, an open-source VHDL reimplementation
of SH-2.
I've split this out from the main J-Core support patches going
upstream through my own linux-sh tree. Changes since the v3 are mainly
cleanup/simplification, inclusion of sched_clock support based on
suggestions by
Signed-off-by: Rich Felker
---
.../devicetree/bindings/timer/jcore,pit.txt| 25 ++
1 file changed, 25 insertions(+)
create mode 100644 Documentation/devicetree/bindings/timer/jcore,pit.txt
diff --git a/Documentation/devicetree/bindings/timer/jcore,pit.txt
Signed-off-by: Rich Felker
---
.../bindings/interrupt-controller/jcore,aic.txt| 26 ++
1 file changed, 26 insertions(+)
create mode 100644
Documentation/devicetree/bindings/interrupt-controller/jcore,aic.txt
diff --git
Hi Myungjoo,
On 2016년 07월 27일 13:27, MyungJoo Ham wrote:
>> This patch adds the new extcon type to group the each connecotr
>> into following five category. This type would be used to handle
>> the connectors as a group unit instead of a connector unit.
>> - EXTCON_TYPE_USB : USB connector
>> -
Signed-off-by: Rich Felker
---
.../bindings/interrupt-controller/jcore,aic.txt| 26 ++
1 file changed, 26 insertions(+)
create mode 100644
Documentation/devicetree/bindings/interrupt-controller/jcore,aic.txt
diff --git
Hi Myungjoo,
On 2016년 07월 27일 13:27, MyungJoo Ham wrote:
>> This patch adds the new extcon type to group the each connecotr
>> into following five category. This type would be used to handle
>> the connectors as a group unit instead of a connector unit.
>> - EXTCON_TYPE_USB : USB connector
>> -
There are two versions of the J-Core interrupt controller in use, aic1
which generates interrupts with programmable priorities, but only
supports 8 irq lines and maps them to cpu traps in the range 17 to 24,
and aic2 which uses traps in the range 64-127 and supports up to 128
irqs, with priorities
There are two versions of the J-Core interrupt controller in use, aic1
which generates interrupts with programmable priorities, but only
supports 8 irq lines and maps them to cpu traps in the range 17 to 24,
and aic2 which uses traps in the range 64-127 and supports up to 128
irqs, with priorities
This driver is used with the J2, an open-source VHDL reimplementation
of SH-2.
I've split this out from the main J-Core support patches going
upstream through my own linux-sh tree. Changes since the v3 stem out
of reworking the DT to use separate reg ranges per cpu rather than
cpu-offset. The
This driver is used with the J2, an open-source VHDL reimplementation
of SH-2.
I've split this out from the main J-Core support patches going
upstream through my own linux-sh tree. Changes since the v3 stem out
of reworking the DT to use separate reg ranges per cpu rather than
cpu-offset. The
On Wed, May 25, 2016 at 08:18:06AM -0500, Rob Herring wrote:
> On Wed, May 25, 2016 at 12:43 AM, Rich Felker wrote:
> > The J-Core project (j-core.org) produces open source cpu and SoC
> > peripheral cores synthesizable as FPGA bitstreams or ASICs.
> >
> > Signed-off-by: Rich
On Wed, May 25, 2016 at 08:18:06AM -0500, Rob Herring wrote:
> On Wed, May 25, 2016 at 12:43 AM, Rich Felker wrote:
> > The J-Core project (j-core.org) produces open source cpu and SoC
> > peripheral cores synthesizable as FPGA bitstreams or ASICs.
> >
> > Signed-off-by: Rich Felker
>
> Please
On Tue, Jul 26, 2016 at 02:31:29PM +0200, Arnd Bergmann wrote:
> The CLOCKSOURCE_OF_DECLARE now takes a function that returns an 'int', but a
> this
> new clocksource driver has just appeared in linux-next and causes a warning
> because
> it has the old 'void' return value:
>
> In file included
On Tue, Jul 26, 2016 at 02:31:29PM +0200, Arnd Bergmann wrote:
> The CLOCKSOURCE_OF_DECLARE now takes a function that returns an 'int', but a
> this
> new clocksource driver has just appeared in linux-next and causes a warning
> because
> it has the old 'void' return value:
>
> In file included
When a bio is cloned, the newly created bio must be associated with
the same blkcg as the original bio (if BLK_CGROUP is enabled). If
this operation is not performed, then the new bio is not associated
with any group, and the group of the current task is returned when
the group of the bio is
When a bio is cloned, the newly created bio must be associated with
the same blkcg as the original bio (if BLK_CGROUP is enabled). If
this operation is not performed, then the new bio is not associated
with any group, and the group of the current task is returned when
the group of the bio is
On Fri, Jul 22, 2016 at 03:01:24PM -0500, Mario Limonciello wrote:
> The Dell Rugged 7202 has 3 programmable buttons (labeled P1, P2, P3)
> and a detachable magnetic keyboard/mouse.
>
> Signed-off-by: Mario Limonciello
+Pali
Pali, any concerns?
> ---
>
On Fri, Jul 22, 2016 at 03:01:24PM -0500, Mario Limonciello wrote:
> The Dell Rugged 7202 has 3 programmable buttons (labeled P1, P2, P3)
> and a detachable magnetic keyboard/mouse.
>
> Signed-off-by: Mario Limonciello
+Pali
Pali, any concerns?
> ---
> drivers/platform/x86/dell-wmi.c | 10
On Tuesday, July 26, 2016 5:33:52 PM EEST Maxime Ripard wrote:
> Hi Stefan,
>
> On Mon, Jul 25, 2016 at 03:37:23PM +0300, Stefan Mavrodiev wrote:
> > A33-OLinuXino is A33 development board designed by Olimex LTD.
> >
> > It has AXP233 PMU, 1GB DRAM, a micro SD card, one USB-OTG connector,
> >
On Tuesday, July 26, 2016 5:33:52 PM EEST Maxime Ripard wrote:
> Hi Stefan,
>
> On Mon, Jul 25, 2016 at 03:37:23PM +0300, Stefan Mavrodiev wrote:
> > A33-OLinuXino is A33 development board designed by Olimex LTD.
> >
> > It has AXP233 PMU, 1GB DRAM, a micro SD card, one USB-OTG connector,
> >
Alexandre Bounine writes:
> Implement changes made in RapidIO specification rev.3 to LP-Serial Physical
> Layer register definitions:
> - use per-port register offset calculations based on LP-Serial Extended
> Features Block (EFB) Register Map type (I or II) with
Alexandre Bounine writes:
> Implement changes made in RapidIO specification rev.3 to LP-Serial Physical
> Layer register definitions:
> - use per-port register offset calculations based on LP-Serial Extended
> Features Block (EFB) Register Map type (I or II) with different per-port
> offset
Hi all,
Today's linux-next merge of the kvm tree got a conflict in:
arch/x86/kvm/vmx.c
between commit:
4e59516a12a6 ("kvm: vmx: ensure VMCS is current while enabling PML")
from Linus' tree and commit:
37e4c997dadf ("KVM: VMX: validate individual bits of guest
Hi all,
Today's linux-next merge of the kvm tree got a conflict in:
arch/x86/kvm/vmx.c
between commit:
4e59516a12a6 ("kvm: vmx: ensure VMCS is current while enabling PML")
from Linus' tree and commit:
37e4c997dadf ("KVM: VMX: validate individual bits of guest
On Tue, Jul 26, 2016 at 11:32:25AM -0700, W. Trevor King wrote:
> On Tue, Jul 26, 2016 at 11:25:24AM -0700, Andrew Vagin wrote:
> > Sure. If a process wants to compare two namespaces, it needs to get file
> > descriptors for them (open /proc/PID/ns/XXX, use new ioctl-s, find a
> > process which
On Tue, Jul 26, 2016 at 11:32:25AM -0700, W. Trevor King wrote:
> On Tue, Jul 26, 2016 at 11:25:24AM -0700, Andrew Vagin wrote:
> > Sure. If a process wants to compare two namespaces, it needs to get file
> > descriptors for them (open /proc/PID/ns/XXX, use new ioctl-s, find a
> > process which
On Tue, Jul 26, 2016 at 02:55:35PM -0700, Kevin Hilman wrote:
> kernelci.org bot writes:
>
> > stable-rc boot: 353 boots: 7 failed, 345 passed with 1 offline
> > (v4.4.15-147-g0b4b25c69607)
> >
> > Full Boot Summary:
> >
On Tue, Jul 26, 2016 at 02:55:35PM -0700, Kevin Hilman wrote:
> kernelci.org bot writes:
>
> > stable-rc boot: 353 boots: 7 failed, 345 passed with 1 offline
> > (v4.4.15-147-g0b4b25c69607)
> >
> > Full Boot Summary:
> >
On Tue, Jul 26, 2016 at 02:27:54PM -0700, Kevin Hilman wrote:
> kernelci.org bot writes:
>
> > stable-rc boot: 670 boots: 4 failed, 662 passed with 3 offline, 1 conflict
> > (v4.6.4-204-g02256e5f7d73)
> >
> > Full Boot Summary:
> >
On Tue, Jul 26, 2016 at 02:27:54PM -0700, Kevin Hilman wrote:
> kernelci.org bot writes:
>
> > stable-rc boot: 670 boots: 4 failed, 662 passed with 3 offline, 1 conflict
> > (v4.6.4-204-g02256e5f7d73)
> >
> > Full Boot Summary:
> >
On Tue, Jul 26, 2016 at 07:05:37PM -0700, k...@exchange.microsoft.com wrote:
> +/*
> + * Create a char device that can support read/write for passing
> + * the payload.
> + */
That sounds "interesting"...
> +
> +static struct completion ip_event;
> +static bool opened;
> +
> +char
On Tue, Jul 26, 2016 at 07:05:37PM -0700, k...@exchange.microsoft.com wrote:
> +/*
> + * Create a char device that can support read/write for passing
> + * the payload.
> + */
That sounds "interesting"...
> +
> +static struct completion ip_event;
> +static bool opened;
> +
> +char
Hi Chanwoo
On 07/27/2016 11:57 AM, Chanwoo Choi wrote:
On 2016년 07월 27일 12:51, Guenter Roeck wrote:
On Tue, Jul 26, 2016 at 8:42 PM, Chanwoo Choi wrote:
Hi Chris,
On 2016년 07월 27일 11:09, Chris Zhong wrote:
Hi Guernter
On 07/27/2016 09:44 AM, Guenter Roeck wrote:
Hi
Hi Chanwoo
On 07/27/2016 11:57 AM, Chanwoo Choi wrote:
On 2016년 07월 27일 12:51, Guenter Roeck wrote:
On Tue, Jul 26, 2016 at 8:42 PM, Chanwoo Choi wrote:
Hi Chris,
On 2016년 07월 27일 11:09, Chris Zhong wrote:
Hi Guernter
On 07/27/2016 09:44 AM, Guenter Roeck wrote:
Hi Chris,
On Tue, Jul
> This patch adds the new extcon type to group the each connecotr
> into following five category. This type would be used to handle
> the connectors as a group unit instead of a connector unit.
> - EXTCON_TYPE_USB : USB connector
> - EXTCON_TYPE_CHG : Charger connector
> - EXTCON_TYPE_JACK :
> This patch adds the new extcon type to group the each connecotr
> into following five category. This type would be used to handle
> the connectors as a group unit instead of a connector unit.
> - EXTCON_TYPE_USB : USB connector
> - EXTCON_TYPE_CHG : Charger connector
> - EXTCON_TYPE_JACK :
On Tue, Jul 26, 2016 at 07:05:37PM -0700, k...@exchange.microsoft.com wrote:
> From: K. Y. Srinivasan
>
> This driver is a bridge driver that surfaces a Mellanox device in the Linux
> guest and plugs into
> the "NetworkDirect" RDMA infrastructure on the Windows host. Only a
On Tue, Jul 26, 2016 at 07:05:37PM -0700, k...@exchange.microsoft.com wrote:
> From: K. Y. Srinivasan
>
> This driver is a bridge driver that surfaces a Mellanox device in the Linux
> guest and plugs into
> the "NetworkDirect" RDMA infrastructure on the Windows host. Only a subset of
> the
Hi all,
On 27 July 2016 at 11:33, Jisheng Zhang wrote:
> +1
>
> On Tue, 26 Jul 2016 09:11:49 -0500 Timur Tabi wrote:
>
>> Will Deacon wrote:
>> > The kernel really needs to support both of those platforms :/
>> >
>> > For the memory-mapped counter registers, the
Hi all,
On 27 July 2016 at 11:33, Jisheng Zhang wrote:
> +1
>
> On Tue, 26 Jul 2016 09:11:49 -0500 Timur Tabi wrote:
>
>> Will Deacon wrote:
>> > The kernel really needs to support both of those platforms :/
>> >
>> > For the memory-mapped counter registers, the architecture says:
>> >
>> >
Hi,
[auto build test WARNING on rdma/master]
[also build test WARNING on v4.7 next-20160726]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/kys-exchange-microsoft-com/Drivers-infiniband-hw
Hi,
[auto build test WARNING on rdma/master]
[also build test WARNING on v4.7 next-20160726]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/kys-exchange-microsoft-com/Drivers-infiniband-hw
Hi,
On Tue, Jul 26, 2016 at 5:13 AM, Caesar Wang wrote:
> This patch adds saradc needed information on rk3399 SoCs.
>
> Signed-off-by: Caesar Wang
> ---
>
> Changes in v2: None
>
> arch/arm64/boot/dts/rockchip/rk3399.dtsi | 12
> 1 file
Hi,
On Tue, Jul 26, 2016 at 5:13 AM, Caesar Wang wrote:
> This patch adds saradc needed information on rk3399 SoCs.
>
> Signed-off-by: Caesar Wang
> ---
>
> Changes in v2: None
>
> arch/arm64/boot/dts/rockchip/rk3399.dtsi | 12
> 1 file changed, 12 insertions(+)
>
> diff --git
Hi Linus,
Could you please consider this pull request?
Thanks,
The following changes since commit 4340fa55298d17049e71c7a34e04647379c269f3:
Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm
(2016-06-02 15:08:06 -0700)
are available in the git repository at:
Hi Linus,
Could you please consider this pull request?
Thanks,
The following changes since commit 4340fa55298d17049e71c7a34e04647379c269f3:
Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm
(2016-06-02 15:08:06 -0700)
are available in the git repository at:
On Tue, Jul 26 2016, Mikulas Patocka wrote:
> On Sat, 23 Jul 2016, NeilBrown wrote:
>
>> "dirtying ... from the reclaim context" ??? What does that mean?
>> According to
>> Commit: 26eecbf3543b ("[PATCH] vm: pageout throttling")
>> From the history tree, the purpose of throttle_vm_writeout() is
On Tue, Jul 26 2016, Mikulas Patocka wrote:
> On Sat, 23 Jul 2016, NeilBrown wrote:
>
>> "dirtying ... from the reclaim context" ??? What does that mean?
>> According to
>> Commit: 26eecbf3543b ("[PATCH] vm: pageout throttling")
>> From the history tree, the purpose of throttle_vm_writeout() is
Hi Linus,
please consider pulling a patch series for 4.8 from:
https://github.com/jgross1/linux.git tags/for-linus-4-8
Support calling functions on dedicated physical cpu
Some hardware (e.g. Dell Studio laptops) require special functions to
be called on physical cpu 0 in order to avoid
Hi Linus,
please consider pulling a patch series for 4.8 from:
https://github.com/jgross1/linux.git tags/for-linus-4-8
Support calling functions on dedicated physical cpu
Some hardware (e.g. Dell Studio laptops) require special functions to
be called on physical cpu 0 in order to avoid
On 2016년 07월 27일 12:51, Guenter Roeck wrote:
> On Tue, Jul 26, 2016 at 8:42 PM, Chanwoo Choi wrote:
>> Hi Chris,
>>
>> On 2016년 07월 27일 11:09, Chris Zhong wrote:
>>> Hi Guernter
>>>
>>> On 07/27/2016 09:44 AM, Guenter Roeck wrote:
Hi Chris,
On Tue, Jul 26,
On 2016년 07월 27일 12:51, Guenter Roeck wrote:
> On Tue, Jul 26, 2016 at 8:42 PM, Chanwoo Choi wrote:
>> Hi Chris,
>>
>> On 2016년 07월 27일 11:09, Chris Zhong wrote:
>>> Hi Guernter
>>>
>>> On 07/27/2016 09:44 AM, Guenter Roeck wrote:
Hi Chris,
On Tue, Jul 26, 2016 at 6:15 PM, Chris
On Tue, Jul 26, 2016 at 2:55 PM, Kees Cook wrote:
> Hi,
>
> This is my next pull request for v4.8, which introduces a kernel self
> protection of copy_to_user/copy_from_user that has been under review and
> test on the kernel-hardening list for a while. It has lived for a
On Tue, Jul 26, 2016 at 2:55 PM, Kees Cook wrote:
> Hi,
>
> This is my next pull request for v4.8, which introduces a kernel self
> protection of copy_to_user/copy_from_user that has been under review and
> test on the kernel-hardening list for a while. It has lived for a bit
> in -next, and
On Tue, Jul 26, 2016 at 8:42 PM, Chanwoo Choi wrote:
> Hi Chris,
>
> On 2016년 07월 27일 11:09, Chris Zhong wrote:
>> Hi Guernter
>>
>> On 07/27/2016 09:44 AM, Guenter Roeck wrote:
>>> Hi Chris,
>>>
>>> On Tue, Jul 26, 2016 at 6:15 PM, Chris Zhong wrote:
On Tue, Jul 26, 2016 at 8:42 PM, Chanwoo Choi wrote:
> Hi Chris,
>
> On 2016년 07월 27일 11:09, Chris Zhong wrote:
>> Hi Guernter
>>
>> On 07/27/2016 09:44 AM, Guenter Roeck wrote:
>>> Hi Chris,
>>>
>>> On Tue, Jul 26, 2016 at 6:15 PM, Chris Zhong wrote:
>>>
>>> [ ... ]
>>>
> > +
>
On Mon, Jul 25 2016, Michal Hocko wrote:
> On Sat 23-07-16 10:12:24, NeilBrown wrote:
>> Maybe that is impractical, but having firm rules like that would go a
>> long way to make it possible to actually understand and reason about how
>> MM works. As it is, there seems to be a tendency to put
On Mon, Jul 25 2016, Michal Hocko wrote:
> On Sat 23-07-16 10:12:24, NeilBrown wrote:
>> Maybe that is impractical, but having firm rules like that would go a
>> long way to make it possible to actually understand and reason about how
>> MM works. As it is, there seems to be a tendency to put
Hi Chris,
On 2016년 07월 27일 11:09, Chris Zhong wrote:
> Hi Guernter
>
> On 07/27/2016 09:44 AM, Guenter Roeck wrote:
>> Hi Chris,
>>
>> On Tue, Jul 26, 2016 at 6:15 PM, Chris Zhong wrote:
>>
>> [ ... ]
>>
> +
> +/* Properties of EXTCON_TYPE_DISP. */
Hi Chris,
On 2016년 07월 27일 11:09, Chris Zhong wrote:
> Hi Guernter
>
> On 07/27/2016 09:44 AM, Guenter Roeck wrote:
>> Hi Chris,
>>
>> On Tue, Jul 26, 2016 at 6:15 PM, Chris Zhong wrote:
>>
>> [ ... ]
>>
> +
> +/* Properties of EXTCON_TYPE_DISP. */
> +#define
+1
On Tue, 26 Jul 2016 09:11:49 -0500 Timur Tabi wrote:
> Will Deacon wrote:
> > The kernel really needs to support both of those platforms :/
> >
> > For the memory-mapped counter registers, the architecture says:
> >
> >`If the implementation supports 64-bit atomic accesses, then the
> >
+1
On Tue, 26 Jul 2016 09:11:49 -0500 Timur Tabi wrote:
> Will Deacon wrote:
> > The kernel really needs to support both of those platforms :/
> >
> > For the memory-mapped counter registers, the architecture says:
> >
> >`If the implementation supports 64-bit atomic accesses, then the
> >
Hi Sebastian,
2016-07-27 11:17 GMT+09:00 Sebastian Reichel :
> Hi,
>
> On Wed, Jul 27, 2016 at 10:23:09AM +0900, Masahiro Yamada wrote:
>> When the kernel fails to boot and its log console is silent,
>> I use earlycon and I often find the cause of error with it.
>>
>> But, I
Hi Sebastian,
2016-07-27 11:17 GMT+09:00 Sebastian Reichel :
> Hi,
>
> On Wed, Jul 27, 2016 at 10:23:09AM +0900, Masahiro Yamada wrote:
>> When the kernel fails to boot and its log console is silent,
>> I use earlycon and I often find the cause of error with it.
>>
>> But, I have been wondering
from Walters's Wife, Deborah writing from my sick bed
This is Walters's wife, Deborah. I am writing this message to you today because
of my Love for the less privileges. As a fellow faithful person like you, it is
my desire and enthusiasm to donate amount of $19.1 million in your hands for a
from Walters's Wife, Deborah writing from my sick bed
This is Walters's wife, Deborah. I am writing this message to you today because
of my Love for the less privileges. As a fellow faithful person like you, it is
my desire and enthusiasm to donate amount of $19.1 million in your hands for a
The current VBD layer reserves buffer space for each attached device based on
three statically configured settings which are read at boot time.
* max_indirect_segs: Maximum amount of segments.
* max_ring_page_order: Maximum order of pages to be used for the shared ring.
* max_queues: Maximum of
The current VBD layer reserves buffer space for each attached device based on
three statically configured settings which are read at boot time.
* max_indirect_segs: Maximum amount of segments.
* max_ring_page_order: Maximum order of pages to be used for the shared ring.
* max_queues: Maximum of
Uninitialized channel pointer causes segmentation fault when we
call free(channel) during cleanup() with no channels initialized.
This happens when you exit early for usage errors. Initialize
the pointer to NULL when it is declared.
Signed-off-by: Alison Schofield
Cc:
Uninitialized channel pointer causes segmentation fault when we
call free(channel) during cleanup() with no channels initialized.
This happens when you exit early for usage errors. Initialize
the pointer to NULL when it is declared.
Signed-off-by: Alison Schofield
Cc: Daniel Baluta
---
Hi Felipe,
On 26 July 2016 at 19:06, Felipe Ferreri Tonello wrote:
> Hi Baolin,
>
> Sorry for not replying for previous emails because for some reason these
> emails were archived. :(
>
> On 12/07/16 10:01, Baolin Wang wrote:
>> Some gadget device (such as dwc3 gadget)
Hi Felipe,
On 26 July 2016 at 19:06, Felipe Ferreri Tonello wrote:
> Hi Baolin,
>
> Sorry for not replying for previous emails because for some reason these
> emails were archived. :(
>
> On 12/07/16 10:01, Baolin Wang wrote:
>> Some gadget device (such as dwc3 gadget) requires
Constant has to be capitalized.
Signed-off-by: Salah Triki
Acked-by: Luis de Bethencourt
---
fs/befs/btree.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/fs/befs/btree.c b/fs/befs/btree.c
index 307645f9..e59ad20 100644
Constant has to be capitalized.
Signed-off-by: Salah Triki
Acked-by: Luis de Bethencourt
---
fs/befs/btree.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/fs/befs/btree.c b/fs/befs/btree.c
index 307645f9..e59ad20 100644
--- a/fs/befs/btree.c
+++ b/fs/befs/btree.c
@@
Since goto statement merely returns NULL, replace it with return
statement.
Signed-off-by: Salah Triki
---
fs/befs/io.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/fs/befs/io.c b/fs/befs/io.c
index 4223b77..af631a6 100644
--- a/fs/befs/io.c
The calls to brelse are useless since dbl_indir_block and indir_block
are NULL.
Signed-off-by: Salah Triki
Acked-by: Luis de Bethencourt
---
fs/befs/datastream.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/fs/befs/datastream.c
The only caller of befs_find_brun_direct is befs_fblock2brun, which
already validates that the block is within the range of direct blocks.
So remove the duplicate validation.
Signed-off-by: Salah Triki
Acked-by: Luis de Bethencourt
---
Since goto statement merely returns NULL, replace it with return
statement.
Signed-off-by: Salah Triki
---
fs/befs/io.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/fs/befs/io.c b/fs/befs/io.c
index 4223b77..af631a6 100644
--- a/fs/befs/io.c
+++ b/fs/befs/io.c
@@
The calls to brelse are useless since dbl_indir_block and indir_block
are NULL.
Signed-off-by: Salah Triki
Acked-by: Luis de Bethencourt
---
fs/befs/datastream.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/fs/befs/datastream.c b/fs/befs/datastream.c
index e224b9a..b68b6f9 100644
---
The only caller of befs_find_brun_direct is befs_fblock2brun, which
already validates that the block is within the range of direct blocks.
So remove the duplicate validation.
Signed-off-by: Salah Triki
Acked-by: Luis de Bethencourt
---
fs/befs/datastream.c | 8
1 file changed, 8
On Tue, Jul 26, 2016 at 09:30:13PM +0100, Luis de Bethencourt wrote:
> >
> > Sounds great! Do you have a git tree set up for your befs development?
>
> Yes, I have the following in github (if that is OK):
> https://github.com/luisbg/linux-befs
>
> I have two branches there based on Linus'
On Tue, Jul 26, 2016 at 09:30:13PM +0100, Luis de Bethencourt wrote:
> >
> > Sounds great! Do you have a git tree set up for your befs development?
>
> Yes, I have the following in github (if that is OK):
> https://github.com/luisbg/linux-befs
>
> I have two branches there based on Linus'
On 2016年07月26日 17:02, Thierry Reding wrote:
On Tue, Jul 26, 2016 at 10:01:32AM +0800, Mark yao wrote:
On 2016年07月25日 23:21, Thierry Reding wrote:
On Wed, Jul 20, 2016 at 11:18:50AM +0800, Mark Yao wrote:
Allow user add display timing on device tree with simple-panel-dsi
On 2016年07月26日 17:02, Thierry Reding wrote:
On Tue, Jul 26, 2016 at 10:01:32AM +0800, Mark yao wrote:
On 2016年07月25日 23:21, Thierry Reding wrote:
On Wed, Jul 20, 2016 at 11:18:50AM +0800, Mark Yao wrote:
Allow user add display timing on device tree with simple-panel-dsi
I have important transaction for you as next of kin to claim US$8.37m Mail me
on my private email: chi...@yahoo.com so i can send you more details
Thanks
Mr.Chim Wai Kim
===
DISCLAIMER: This email and any
I have important transaction for you as next of kin to claim US$8.37m Mail me
on my private email: chi...@yahoo.com so i can send you more details
Thanks
Mr.Chim Wai Kim
===
DISCLAIMER: This email and any
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
arch/arm64/boot/dts/apm/apm-shadowcat.dtsi
between commit:
cafc4cd0c8b8 ("arm64: dts: apm: Use lowercase consistently for hex constants")
from the arm-soc tree and commit:
8e694cd2762c ("dtb: xgene: Add MDIO
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
arch/arm64/boot/dts/apm/apm-shadowcat.dtsi
between commit:
cafc4cd0c8b8 ("arm64: dts: apm: Use lowercase consistently for hex constants")
from the arm-soc tree and commit:
8e694cd2762c ("dtb: xgene: Add MDIO
1 - 100 of 1398 matches
Mail list logo