We don't have a real use-case for this. Understanding the consequences,
we are questioning the patch in downstream itself.
Please ignore this patch for now.
On 12/12/18 1:36 PM, Christoph Hellwig wrote:
scatterlist elements longer than 4GB sound odd. Please submit it
in a series with your
On Sun, Dec 23, 2018 at 12:54:11PM +0200, Thomas Backlund wrote:
> Den 23-12-2018 kl. 01:28, skrev Linus Torvalds:
> > On Sat, Dec 22, 2018 at 3:07 PM Christian Brauner
> > wrote:
> > >
> > > However, for this case should I resend the revert?
> >
> > Since I was pointed at the original email
On Sat 22-12-18 09:04:21, Nicholas Mc Guire wrote:
> On Fri, Dec 21, 2018 at 01:58:39PM -0800, David Rientjes wrote:
> > On Thu, 20 Dec 2018, Nicholas Mc Guire wrote:
> >
> > > diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> > > index 871e41c..1c118d7 100644
> > > --- a/mm/vmalloc.c
> > > +++
4.20 release is affected too.
On Sun, 2018-12-23 at 20:29 +0500, Ivan Mironov wrote:
> This happened when I tried to boot normal Fedora 29 system with latest
> available kernel (from fedora rawhide, plus some unrelated custom
> patches):
>
> BUG: unable to handle kernel NULL pointer
Hello!
On 24.12.2018 9:52, Mason Yang wrote:
Document the bindings used by the Renesas R-Car Gen3 RPC controller.
Signed-off-by: Mason Yang
---
.../devicetree/bindings/spi/spi-renesas-rpc.txt| 37 ++
1 file changed, 37 insertions(+)
create mode 100644
On 2018/12/22 19:08, Martin Blumenstingl wrote:
> On Sat, Dec 22, 2018 at 8:00 AM kbuild test robot wrote:
>>
>> Hi Martin,
>>
>> Thank you for the patch! Perhaps something to improve:
>>
>> [auto build test WARNING on f2fs/dev-test]
>> [also build test WARNING on v4.20-rc7 next-20181221]
>> [if
Now, as Google's user guide, if userspace need clean ION buffer's
cache, they should call ioctl(fd, DMA_BUF_IOCTL_SYNC, sync). Then
we found that ion_dma_buf_begin_cpu_access/ion_dma_buf_end_cpu_access
will do ION buffer's map_kernel, it's not necessary. And if usersapce
only need clean cache,
On Fri, Dec 21, 2018 at 08:21:49AM -0800, Guenter Roeck wrote:
> ---
> [5]:
>
> The bisect is old, but still applies. Revering the offending patch fixes the
> problem.
>
> # bad: [8c9733fd9806c71e7f2313a280f98cb3051f93df] Add linux-next specific
> files for 20181123
> # good:
ср, 12 дек. 2018 г. в 20:41, Ezequiel Garcia :
>
> On Wed, 12 Dec 2018 at 14:27, Laurent Pinchart
> wrote:
> >
> > Hi Matwey,
> >
> > Thank you for the patches.
> >
> > For the whole series,
> >
> > Reviewed-by: Laurent Pinchart
> >
>
> Thanks Laurent.
>
> Matwey, given your detailed analysis of
On 2018/12/14 下午8:33, Michael S. Tsirkin wrote:
On Fri, Dec 14, 2018 at 11:42:18AM +0800, Jason Wang wrote:
On 2018/12/13 下午11:27, Michael S. Tsirkin wrote:
On Thu, Dec 13, 2018 at 06:10:19PM +0800, Jason Wang wrote:
Hi:
This series tries to access virtqueue metadata through kernel virtual
From: "huang.zijiang"
memblock_alloc never returns NULL because panic never returns
Signed-off-by: huang.zijiang
---
drivers/firmware/memmap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/firmware/memmap.c b/drivers/firmware/memmap.c
index d168c87..ec4fd25
Add EC host commands to control codec on EC.
Signed-off-by: Cheng-Yi Chiang
Signed-off-by: Lee Jones
---
Note: This patch is merged to mfd tree for-mfd-next branch already.
But this is still needed on sound tree for-next branch in order to
compile codec driver.
From: "huang.zijiang"
kmemdup has implemented the function that kmalloc() and memcpy().
Signed-off-by: huang.zijiang
---
sound/pci/emu10k1/emufx.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/sound/pci/emu10k1/emufx.c b/sound/pci/emu10k1/emufx.c
index 6ebe817..b4fe4c5
Add documentation for Chrome EC codec driver.
Signed-off-by: Cheng-Yi Chiang
---
Change in v2: Fixed name of driver in MAINTAINERS.
.../bindings/sound/google,cros-ec-codec.txt | 24 +++
MAINTAINERS | 5
2 files changed, 29
Hi,
On Fri, 2018-12-21 at 17:56 +0100, meg...@megous.com wrote:
> From: Ondrej Jirman
>
> When cedrus_hw_probe is called, v4l2_dev is not yet initialized.
> Use dev_err instead.
Good catch and thanks for the patch!
Acked-by: Paul Kocialkowski
Cheers,
Paul
> Signed-off-by: Ondrej Jirman
>
On 2018/12/17 上午3:57, Michael S. Tsirkin wrote:
On Sat, Dec 15, 2018 at 11:43:08AM -0800, David Miller wrote:
From: Jason Wang
Date: Fri, 14 Dec 2018 12:29:54 +0800
On 2018/12/14 上午4:12, Michael S. Tsirkin wrote:
On Thu, Dec 13, 2018 at 06:10:19PM +0800, Jason Wang wrote:
Hi:
This
Add a codec driver to control ChromeOS EC codec.
Use EC Host command to enable/disable I2S recording and control other
configurations.
Signed-off-by: Cheng-Yi Chiang
---
Addressed Enric's comments.
Changes in v2:
- Many style fixes. Passed checkpatch.pl --strict.
- Use ChromeOS naming.
-
On Thu, Nov 29, 2018 at 8:42 PM Enric Balletbo Serra
wrote:
>
> Hi Cheng-Yi
>
> Many thanks for the patch. I am not really an ASoC expert, so my
> comments are more based on the feedback for other cros-ec drivers. So,
> various nits and few comments below.
>
Hi Enric,
Thank you for the review
Introduce shutdown-irq binding required for sysmon shutdown for Q6V5 MSS
on SDM845/MSM8996 SoCs and for WCSS Q6V5 on QCS404 SoC.
Signed-off-by: Sibi Sankar
---
v2:
Make shutdown-ack mandatory for MSS on SDM845/MSM8996 and
for WCSS on QCS404 (Dropping Rob's reviewed-by due to this)
Add shutdown-ack irq handling for Q6V5. This patch includes enabling
shutdown-ack irq on those Q6V5 instances with "has_shutdown_irq"
flag set and exposing Q6V5 state information to the sysmon instance
which is required to ascertain graceful shutdown completion.
Signed-off-by: Sibi Sankar
---
Enable shutdown-ack irq handling for MSS Q6V5 on SDM845/MSM8996
SoCs and for WCSS Q6V5 on QCS404 SoC.
Signed-off-by: Sibi Sankar
---
drivers/remoteproc/qcom_q6v5_mss.c | 11 ---
drivers/remoteproc/qcom_q6v5_pas.c | 9 +++--
2 files changed, 15 insertions(+), 5 deletions(-)
diff
After sending a sysmon shutdown request to the SSCTL service on the
subsystem, wait for the service to send shutdown-ack interrupt or
an indication message to signal the completion of graceful shutdown.
Signed-off-by: Sibi Sankar
---
drivers/remoteproc/qcom_sysmon.c | 40
> -Original Message-
> From: YueHaibing
> Sent: Thursday, December 20, 2018 8:46 AM
> To: qlogic-storage-upstr...@qlogic.com; j...@linux.ibm.com;
> martin.peter...@oracle.com
> Cc: linux-kernel@vger.kernel.org; linux-s...@vger.kernel.org; YueHaibing
>
> Subject: [EXT] [PATCH -next]
Hi,
On Fri, 2018-12-21 at 09:52 -0800, Florian Fainelli wrote:
> On 12/21/18 4:11 AM, Paul Kocialkowski wrote:
> > The driver's interrupt handler checks whether a message is currently
> > being handled with the curr_msg pointer. When it is NULL, the interrupt
> > is considered to be unexpected.
Hi,
On 22-12-18 21:26, Wolfram Sang wrote:
Here is the new version without specific I2C helpers but using the
'is_suspended' flag from the PM core. I didn't like messing with the
flag directly, so I did a helper in patch 1. So far, I like the
approach. The diffstat looks nice, and i2c-rcar.c
This is the 2nd patchset for komeda-driver.
These patches focus on CHIP(D71) Layer for pipeline/component descovery and
initialization. All basic and essential display component: layer, compiz,
improc, timing-ctrlr and irq handling have been added, other component
support: scaler, wb_layer,
1. Add detailed layer/layer_state definitions
2. Add d71_layer_init to report layer features and capabilities according
to D71 layer block.
3. Add d71_layer_updat/disable
Signed-off-by: James (Qian) Wang
---
.../drm/arm/display/include/malidp_utils.h| 17 ++
D71 consists of a number of Register Blocks, every Block controls a
specific HW function, every block has a common block_header to represent
its type and pipeline information.
GCU (Global Control Unit) is the first Block which describe the global
information of D71 HW, Like number of block
Add and initialize improc and timing_ctrlr according to D71 capablitites
Signed-off-by: James (Qian) Wang
---
.../arm/display/komeda/d71/d71_component.c| 108 +-
.../gpu/drm/arm/display/komeda/komeda_kms.h | 2 +
.../drm/arm/display/komeda/komeda_pipeline.h | 7 ++
3
Implement d71_compiz_init and add compiz component to komeda-CORE
Signed-off-by: James (Qian) Wang
---
.../arm/display/komeda/d71/d71_component.c| 95 ++-
.../drm/arm/display/komeda/komeda_pipeline.h | 26 +++--
2 files changed, 113 insertions(+), 8 deletions(-)
diff --git
komeda_accemble_pipelines is for:
1. Verifing the component->supported_inputs according to the
pipeline->avail_components.
2. Generating component->supported_outputs.
Signed-off-by: James (Qian) Wang
---
.../gpu/drm/arm/display/komeda/komeda_dev.c | 6 ++
Add a debugfs node "register" and entry function dump_register to
dev/pipeline/component to register dump, then user can read
"/sys/kernel/debug/komeda/register" to get the register values via these
chip function.
Signed-off-by: James (Qian) Wang
---
.../arm/display/komeda/d71/d71_component.c
1. Added irq_handler/irq_enable/irq_disable to komeda_dev_func, then the
Komeda-CORE can control the HW irq via these chip function.
2. Install irq and register irq_handler to system by DRM, so once the IRQ
coming, the handling sequence is:
komeda_kms_irq_handler(int irq, void *data)
On 12/24/2018 12:02 PM, Lee Jones wrote:
On Sun, 23 Dec 2018, Tony Lindgren wrote:
* Lee Jones [181221 11:01]:
On Tue, 18 Dec 2018, Christian Hohnstaedt wrote:
These options apply to all regulators in this chip.
strict-supply-voltage:
Set STRICT flag in CONFIG1
under-voltage-limit:
From: Ajit Pandey
Platform DAI component probe is not called if it is not
present in component list during sound card registration.
Check if component is registered for platform dai before
soundcard registration.
Signed-off-by: Ajit Pandey
Signed-off-by: Rohit kumar
---
On 11/28/18, 10:03 AM, "linux-scsi-ow...@vger.kernel.org on behalf of
Gustavo A. R. Silva" wrote:
>External Email
>
>In preparation to enabling -Wimplicit-fallthrough, mark switch cases
>where we are expecting to fall through.
>
>Notice that, in this particular case, I replaced "allow
Platform DAI component probe is not called if it is not
present in component list during sound card registration.
Add snd_soc_of_lookup_component() to get component info from
device_node. This can be used by machine driver to make sure that
card components are registered before calling
From: Ajit Pandey
Soundcard should be registered after all components are registered.
Add snd_soc_of_lookup_component() to get component info from
device_node. This can be used by machine driver to make sure that
card components are registered before calling snd_soc_register_card().
> -Original Message-
> From: Gustavo A. R. Silva [mailto:gust...@embeddedor.com]
> Sent: Monday, December 24, 2018 2:40 PM
>
> One of the more common cases of allocation size calculations is finding the
> size of a structure that has a zero-sized array at the end, along with memory
> for
With current retry mechanism in f2fs_fill_super, first fill_super
fails due to no memory, then second fill_super runs w/o recovery,
if we succeed, we may lose fsynced data, it doesn't make sense.
Let's retry fill_super only if it occurs non-ENOMEM error during
recovery.
Signed-off-by: Chao Yu
Hi,
On Sat, 2018-12-22 at 13:19 +0100, Stefan Wahren wrote:
> Hi Paul,
>
> > Paul Kocialkowski hat am 21. Dezember 2018
> > um 13:11 geschrieben:
> >
> >
> > The driver's interrupt handler checks whether a message is currently
> > being handled with the curr_msg pointer. When it is NULL, the
From: Michal Hocko
Burt Holzman has noticed that memcg v1 doesn't notify about OOM events
via eventfd anymore. The reason is that 29ef680ae7c2 ("memcg, oom: move
out_of_memory back to the charge path") has moved the oom handling back
to the charge path. While doing so the notification was left
On Sun, Dec 23, 2018 at 05:49:54PM +0100, Marcus Meissner wrote:
> Hi,
>
> I am the maintainer of libmtp and libgphoto2
>
> Some months ago I was made aware of this bug:
> https://bugs.kde.org/show_bug.cgi?id=387454
>
> This was fallout identified to come from this kernel commit:
>
>
On 12/18/2018 1:35 PM, Christian Hohnstaedt wrote:
Add input voltage configuration options
Signed-off-by: Christian Hohnstaedt
---
Documentation/devicetree/bindings/regulator/tps65218.txt | 10 ++
1 file changed, 10 insertions(+)
diff --git
This is the 3rd patchset for the komeda driver.
This patchset implemented plane/plane_helper functions for DRM-Plane.
per the komeda driver design, A DRM-plane maps to komeda layer input
pipeline, so the plane->atomic_check will build a layer input pipeline
according to the plane_state. and with
get_state_and_set_user packed get_state and set_user into one function,
which get pipeline/component state for a specific pipeline/component, if
success set the user to it.
Signed-off-by: James (Qian) Wang
---
drivers/gpu/drm/arm/display/komeda/Makefile | 1 +
Initialize koemda_layer, komeda_compiz, komeda_improc and
komeda_timing_ctrlr as drm private object, then track komeda private
component state by drm_atomic_state.
Signed-off-by: James (Qian) Wang
---
.../arm/display/komeda/komeda_private_obj.c | 200 +-
1 file changed, 198
This pair of functions return the old/new private object state for the
given private_obj, or NULL if the private_obj is not part of the global
atomic state.
Reviewed-by: Alexandru Gheorghe
Signed-off-by: James (Qian) Wang
---
drivers/gpu/drm/drm_atomic.c | 45
Per komeda design KMS-plane maps to komeda layer input pipeline.
komeda_plane_atomic_check is for building a komeda layer input pipeline.
And KMS-plane is only a user of komeda resources. so there is no real HW
update for plane, but all HW update will be handled in crtc->flush.
Signed-off-by:
build_layer_data_flow builds a input pipeline according to plane_state.
and in this initial stage only added this simplest pipeline usage:
Layer -> compiz
The scaler and layer_split will be added in the future.
Signed-off-by: James (Qian) Wang
---
.../drm/arm/display/komeda/komeda_pipeline.h
On Mon, Dec 24, 2018 at 08:31:27AM +0100, Gabriel C wrote:
> Am So., 23. Dez. 2018 um 19:09 Uhr schrieb Dmitry Torokhov
> :
>
> [ also added Linus to CC on that one too ]
> >
> > On Sun, Dec 23, 2018 at 06:17:04PM +0100, Christian Brauner wrote:
> > > On Sun, Dec 23, 2018 at 05:49:54PM +0100,
On Mon, Dec 24, 2018 at 08:31:27AM +0100, Gabriel C wrote:
> Am So., 23. Dez. 2018 um 19:09 Uhr schrieb Dmitry Torokhov
> :
>
> [ also added Linus to CC on that one too ]
> >
> > On Sun, Dec 23, 2018 at 06:17:04PM +0100, Christian Brauner wrote:
> > > On Sun, Dec 23, 2018 at 05:49:54PM +0100,
Am Samstag, 22. Dezember 2018, 17:42:49 CET schrieb Katsuhiro Suzuki:
> This patch fixes settings of GPLL frequency in fractional mode for
> rk3328. In this mode, FOUTVCO is calcurated by following formula:
> FOUTVCO = FREF * FBDIV / REFDIV + ((FREF * FRAC / REFDIV) >> 24)
>
> The problem is in
On Mon, Dec 24, 2018 at 10:12:29AM +0100, Greg KH wrote:
> On Sun, Dec 23, 2018 at 05:49:54PM +0100, Marcus Meissner wrote:
> > Hi,
> >
> > I am the maintainer of libmtp and libgphoto2
> >
> > Some months ago I was made aware of this bug:
> > https://bugs.kde.org/show_bug.cgi?id=387454
> >
A komeda flush is comprised two steps:
1. update pipeline/component state to HW.
2. call dev_func->flush to notify HW to kickoff the update.
Signed-off-by: James (Qian) Wang
---
.../gpu/drm/arm/display/komeda/d71/d71_dev.c | 11 ++
.../gpu/drm/arm/display/komeda/komeda_crtc.c | 33
These two function will be used by komeda_crtc_enable/disable to do some
prepartion works when enable/disable a crtc. like enable a crtc:
1. Adjust display operation mode.
2. Enable/prepare needed clk.
Signed-off-by: James (Qian) Wang
---
.../gpu/drm/arm/display/komeda/d71/d71_dev.c | 32
komeda_crtc_mode_valid compares the input mode->clk with main engine clk
and AXI clk, and reject the mode if the required pixel clk can not be
satisfied by main engine clk and AXI-clk.
Signed-off-by: James (Qian) Wang
---
.../gpu/drm/arm/display/komeda/komeda_crtc.c | 52 +++
1
Komeda driver treats KMS-CRTC/PLANE as user which will acquire pipeline
resources, but we still need to release the unclaimed resources.
crtc_atomic_check is the final check stage, so beside build a display data
pipeline according the crtc_state, but still needs to release/disable the
unclaimed
This function builds a display output pipeline according to crtc_state.
And this change only added single pipeline support, the dual pipeline with
slave enabled data flow support will be added in the following change.
Signed-off-by: James (Qian) Wang
---
This is the 4th patchset for komeda-driver, with this patchset the driver
can bring up and enable the D71 support with basic features.
This patchset implemented komeda_crtc/crtc_helper functions for
DRM-crtc.
James (Qian) Wang (11):
drm/komeda: Add komeda_build_display_data_flow
drm/komeda:
Pass enable/disable command to komeda and adjust komeda hardware for
enable/disable a display instance.
Signed-off-by: James (Qian) Wang
---
.../gpu/drm/arm/display/komeda/komeda_crtc.c | 102 +-
.../gpu/drm/arm/display/komeda/komeda_kms.h | 3 +
Add a new komeda_dev_func->on_off_vblank to enable/disable HW vblank event
Signed-off-by: James (Qian) Wang
---
.../gpu/drm/arm/display/komeda/d71/d71_dev.c | 10 ++
.../gpu/drm/arm/display/komeda/komeda_crtc.c | 19 +++
.../gpu/drm/arm/display/komeda/komeda_dev.h |
Implement komeda_kms_check to add all affected_planes (even unchanged) to
drm_atomic_state. since komeda need to re-calculate the resources
assumption in every commit.
Signed-off-by: James (Qian) Wang
---
.../gpu/drm/arm/display/komeda/komeda_kms.c | 30 ++-
1 file changed, 29
Add two sysfs node: core_id, config_id, user can read them to fetch the
HW product information.
Signed-off-by: James (Qian) Wang
---
.../drm/arm/display/include/malidp_product.h | 12 +
.../gpu/drm/arm/display/komeda/komeda_dev.c | 48 +++
Added functions:
- komeda_crtc_reset
- komeda_crtc_vblank_enable
- komeda_crtc_vblank_disable
Signed-off-by: James (Qian) Wang
---
.../gpu/drm/arm/display/komeda/komeda_crtc.c | 48 +++
1 file changed, 48 insertions(+)
diff --git
CHIP set bus_width according to the HW configuration, and CORE will use
it as buffer alignment.
Signed-off-by: James (Qian) Wang
---
drivers/gpu/drm/arm/display/komeda/d71/d71_dev.c | 1 +
drivers/gpu/drm/arm/display/komeda/komeda_kms.c | 6 +++---
2 files changed, 4 insertions(+), 3
On Sun, Dec 23, 2018 at 6:15 PM Lukas Wunner wrote:
>
> On Sun, Dec 23, 2018 at 02:00:15AM +0300, Sinan Kaya wrote:
> > On Sat, Dec 22, 2018 at 7:40 PM Lukas Wunner wrote:
> > > On Sat, Dec 22, 2018 at 09:07:12AM +, Sinan Kaya wrote:
> > > > This driver depends on the PCI infrastructure but
On 21.12.2018 23:47, Rob Herring wrote:
> On Thu, Dec 20, 2018 at 5:38 AM Andrzej Hajda wrote:
>> On 20.12.2018 12:14, Greg Kroah-Hartman wrote:
>>> On Thu, Dec 20, 2018 at 11:22:45AM +0100, Andrzej Hajda wrote:
During probe every time driver gets resource it should usually check for
On 24.12.2018 04:42, Aditya Pakki wrote:
> In net_ns_init(), register_pernet_subsys() could fail while registering
> network namespace subsystems. The fix checks the return value and
> sends a panic() on failure.
>
> Signed-off-by: Aditya Pakki
Reviewed-by: Kirill Tkhai
> ---
>
On Fri, Dec 21, 2018 at 8:53 PM Ross Zwisler wrote:
>
> On Fri, Dec 21, 2018 at 11:23:07AM -0800, Dhinakaran Pandiyan wrote:
> > On Fri, 2018-12-21 at 10:23 -0700, Ross Zwisler wrote:
> > > The following commit:
> > >
> > > commit 2bdd045e3a30 ("drm/i915/psr: Check if VBT says PSR can be
> > >
On Mon, Dec 24, 2018 at 01:22:57AM -0800, Dmitry Torokhov wrote:
> On Mon, Dec 24, 2018 at 10:12:29AM +0100, Greg KH wrote:
> > On Sun, Dec 23, 2018 at 05:49:54PM +0100, Marcus Meissner wrote:
> > > Hi,
> > >
> > > I am the maintainer of libmtp and libgphoto2
> > >
> > > Some months ago I was
On Sun, Dec 23, 2018 at 09:57:02AM +0100, Julia Lawall wrote:
> Drop LIST_HEAD where the variable it declares is never used.
>
> tmp_list has been declared since the introduction of the driver
> and has never been used. The two declarations of list were
> introduced with the containing functions
On Mon, Dec 24, 2018 at 09:10:56AM +0100, Michal Hocko wrote:
> On Sat 22-12-18 09:04:21, Nicholas Mc Guire wrote:
> > On Fri, Dec 21, 2018 at 01:58:39PM -0800, David Rientjes wrote:
> > > On Thu, 20 Dec 2018, Nicholas Mc Guire wrote:
> > >
> > > > diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> > > >
On Sat, 22 Dec 2018 at 12:04, Ard Biesheuvel wrote:
>
> On Sat, 22 Dec 2018 at 11:54, Ingo Molnar wrote:
> >
> >
> > * Sai Praneeth Prakhya wrote:
> >
> > > Commit d5052a7130a6 ("x86/efi: Unmap EFI boot services code/data regions
> > > from efi_pgd") forgets to take two EFI modes into
On 12/21/2018 4:31 PM, Lee Jones wrote:
On Tue, 18 Dec 2018, Christian Hohnstaedt wrote:
These options apply to all regulators in this chip.
strict-supply-voltage:
Set STRICT flag in CONFIG1
under-voltage-limit:
Select 2.75, 2.95, 3.25 or 3.35 V UVLO in CONFIG1
On Mon, 24 Dec 2018 at 08:40, Yueyi Li wrote:
>
> When KASLR enaled(CONFIG_RANDOMIZE_BASE=y), the top 4K virtual
> address have chance to be mapped to physical address, but which
> is expected to leave room for ERR_PTR.
>
> Also, it might cause some other warparound issue when somewhere
> use the
On Fri, Dec 21, 2018 at 03:26:26PM -0800, Amir Mahdi Ghorbanian wrote:
> Replaced bool in struct with unsigned int bitfield to conserve space and
> more clearly define size of varibales
>
> Signed-off-by: Amir Mahdi Ghorbanian
> ---
There was some discussion on this at Outreachy list:
Replaced text ---help--- with help as per style check patch recommendation
Signed-off-by: Daniel
---
drivers/staging/speakup/Kconfig | 32
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/drivers/staging/speakup/Kconfig
On Sat, Dec 22, 2018 at 02:30:11PM -0800, Mike Kravetz wrote:
> There are two primary issues addressed here:
> 1) For shared pmds, huge PTE pointers returned by huge_pte_alloc can become
>invalid via a call to huge_pmd_unshare by another thread.
> 2) hugetlbfs page faults can race with
Am Mo., 24. Dez. 2018 um 10:17 Uhr schrieb Greg KH :
>
> On Mon, Dec 24, 2018 at 08:31:27AM +0100, Gabriel C wrote:
> > Am So., 23. Dez. 2018 um 19:09 Uhr schrieb Dmitry Torokhov
> > :
> >
> > [ also added Linus to CC on that one too ]
> > >
> > > On Sun, Dec 23, 2018 at 06:17:04PM +0100,
On Fri, Nov 30, 2018 at 11:11:01AM -0500, Yangtao Li wrote:
> Use DEFINE_SHOW_ATTRIBUTE macro to simplify the code.
>
> Signed-off-by: Yangtao Li
Sorry, fell through the cracks, applied for 4.22, thanks for your patch.
For next time around pls ping again after 1-2 weeks already, instead of
1-2
According to adjust the position of variables in kvm_vcpu_arch,
the size of kvm_vcpu can reduce 16 bytes.
before:
cat /proc/slabinfo | grep kvm
kvm_vcpu 252252 9120 28 ...
after:
cat /proc/slabinfo | grep kvm
kvm_vcpu 28 28 9104 28 ...
Signed-off-by: Peng Hao
---
Hi,
Rose device crashes kernel after several seconds after up'ping. I am doing just:
# ip link set dev rose0 address 11:22:33:44:55
# ip link set dev rose0 up
Then after ~15 seconds or so:
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
Am Mo., 24. Dez. 2018 um 10:17 Uhr schrieb Dmitry Torokhov
:
>
> On Mon, Dec 24, 2018 at 08:31:27AM +0100, Gabriel C wrote:
> > Am So., 23. Dez. 2018 um 19:09 Uhr schrieb Dmitry Torokhov
> > :
> >
> > [ also added Linus to CC on that one too ]
> > >
> > > On Sun, Dec 23, 2018 at 06:17:04PM +0100,
On Fri, Dec 21, 2018 at 02:35:05PM +, Lee Jones wrote:
> > + if (ioeic_val) {
> > + tqmx86_writeb(pld, ioeic_val, TQMX86_IOEIC);
> > + if (tqmx86_readb(pld, TQMX86_IOEIC) != ioeic_val) {
> > + dev_warn(pld->dev,
> > +"i2c/gpio
On Mon, Dec 24, 2018 at 11:15:34AM +0100, Gabriel C wrote:
> Am Mo., 24. Dez. 2018 um 10:17 Uhr schrieb Greg KH
> :
> >
> > On Mon, Dec 24, 2018 at 08:31:27AM +0100, Gabriel C wrote:
> > > Am So., 23. Dez. 2018 um 19:09 Uhr schrieb Dmitry Torokhov
> > > :
> > >
> > > [ also added Linus to CC on
On Sat, Dec 22, 2018 at 01:00:46PM +, Colin King wrote:
> From: Colin Ian King
>
> In the case where state cannot be allocated, the current exit path via
> label 'out' will dereference the null state pointer when calling
> drm_atomic_state_put. Fix this by adding a new error exit label and
>
The following changes since commit
ccda4af0f4b92f7b4c308d3acc262f4a7e3affad:
Linux 4.20-rc2 (2018-11-11 17:12:31 -0600)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git
tags/locks-v4.21-1
for you to fetch changes up to
On Sun, Dec 23, 2018 at 03:35:49PM +0100, Christian Brauner wrote:
> Since binderfs can be mounted by userns root in non-initial user namespaces
> some precautions are in order. First, a way to set a maximum on the number
> of binder devices that can be allocated per binderfs instance and second,
Hi Linus,
The following changes since commit 651022382c7f8da46cb4872a545ee1da6d097d2a:
Linux 4.20-rc1 (2018-11-04 15:37:52 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/thierry.reding/linux-pwm.git
tags/pwm/for-4.21-rc1
for you to fetch
Hi all,
Just one more :-)
News: there will be no linux-next release until Jan 2. Have a good break.
Changes since 20181221:
The mips-fixes tree gained a conflict against Linus' tree.
The kbuild tree gained a conflict against the mips-fixes tree.
The rdma tree gained a conflict against the
Am 21.12.18 um 08:07 schrieb Kangjie Lu:
> mt312_reset() may fail. Although it is called in the end of
> mt312_set_frontend(), we better check its status and return its error
> code upstream instead of 0.
>
> Signed-off-by: Kangjie Lu
Thanks for submitting this patch. It looks correct.
Am Mo., 24. Dez. 2018 um 11:54 Uhr schrieb Greg KH :
>
> On Mon, Dec 24, 2018 at 11:15:34AM +0100, Gabriel C wrote:
> > Am Mo., 24. Dez. 2018 um 10:17 Uhr schrieb Greg KH
> > :
> > >
> > > On Mon, Dec 24, 2018 at 08:31:27AM +0100, Gabriel C wrote:
> > > > Am So., 23. Dez. 2018 um 19:09 Uhr
> On Dec 24, 2018, at 12:49 AM, Michal Hocko wrote:
>
> [Cc-ing mailing list and people involved in the original patch]
>
> On Fri 21-12-18 13:42:24, Paul Oppenheimer wrote:
>> Hello! I've never reported a kernel bug before, and since its on the
>> "next" tree I was told to email the author
When handling ept misconfig exit, it will call emulate instruction
with insn_len = 0. The decode instruction function may return a fetch
fault and should propagate to guest.
The problem will result to emulation fail.
KVM internal error. Suberror: 1
emulation failure
EAX=f81a0024 EBX=f6a07000
On Thu, 2018-12-20 at 12:20 -0600, Bjorn Helgaas wrote:
> On Tue, Dec 18, 2018 at 05:19:24PM +0800, Jianjun Wang wrote:
> > On Mon, 2018-12-17 at 15:46 +, Lorenzo Pieralisi wrote:
> > > On Mon, Dec 17, 2018 at 08:32:47AM -0600, Bjorn Helgaas wrote:
> > > > On Mon, Dec 17, 2018 at 04:19:39PM
On Mon, Dec 24, 2018 at 12:09:37PM +0100, Christian Brauner wrote:
> On Sun, Dec 23, 2018 at 03:35:49PM +0100, Christian Brauner wrote:
> > Since binderfs can be mounted by userns root in non-initial user namespaces
> > some precautions are in order. First, a way to set a maximum on the number
> >
Hi all,
Commit
87410161a381 ("cifs: check kzalloc return")
is missing a Signed-off-by from its author.
--
Cheers,
Stephen Rothwell
pgpkCRUe8DnoF.pgp
Description: OpenPGP digital signature
On Mon, Dec 24, 2018 at 12:45:59PM +0100, Greg KH wrote:
> On Mon, Dec 24, 2018 at 12:09:37PM +0100, Christian Brauner wrote:
> > On Sun, Dec 23, 2018 at 03:35:49PM +0100, Christian Brauner wrote:
> > > Since binderfs can be mounted by userns root in non-initial user
> > > namespaces
> > > some
On Sun, Dec 23, 2018 at 12:42:48PM -0800, Andy Lutomirski wrote:
> On Sun, Dec 23, 2018 at 4:52 AM Jarkko Sakkinen
> wrote:
> >
> > On Sat, Dec 22, 2018 at 10:25:02AM +0200, Jarkko Sakkinen wrote:
> > > On Sat, Dec 22, 2018 at 10:16:49AM +0200, Jarkko Sakkinen wrote:
> > > > On Thu, Dec 20, 2018
1 - 100 of 310 matches
Mail list logo
