From: Chen Yu
ThinkPad X1 Tablet(2016) is reported to have issues with
the Low Power S0 Idle _DSM interface and since this machine
model generally can do ACPI S3 just fine, and user would
like to use S3 as default sleep model, add a blacklist
entry to disable that interface
Hi Nicolin,
On Sun, Apr 8, 2018 at 8:57 PM, Nicolin Chen wrote:
> When the desired ratio is less than 256, the savesub (tolerance)
> in the calculation would become 0. This will then fail the loop-
> search immediately without reporting any errors.
>
> But if the ratio is
On Mon, Apr 9, 2018 at 9:57 AM, Dmitry Vyukov wrote:
> On Mon, Apr 9, 2018 at 7:40 AM, Stephan Mueller wrote:
>> Am Montag, 9. April 2018, 00:46:03 CEST schrieb Theodore Y. Ts'o:
>>
>> Hi Theodore,
>>>
>>> So the syzbot will run while the patch goes
However my fundamental concerns about the policy whether to disable the sched
tick remain:
Mixing the precise timer and vague heuristic for the decision is
dangerous. The timer should not be wrong, heuristic may be.
Well, I wouldn't say "dangerous". It may be suboptimal, but even that is not
On Tue, Apr 10, 2018 at 5:29 AM, Lukasz Majewski wrote:
> This commit adds support for AUO's 7.0" display.
>
> Signed-off-by: Lukasz Majewski
>
> ---
> Changes for v2:
> - Add *.txt suffix to the auo,g070wn01 file
> - Remove not needed bus-format-override =
Am Montag, 26. März 2018, 11:00:01 CEST schrieb Tomeu Vizoso:
> devm_regulator_get_optional returns -ENODEV if the regulator isn't
> there, so if that's the case we have to make sure not to leave -ENODEV
> in the regulator pointer.
>
> Also, make sure we return 0 in that case, but correctly
On Tue, Apr 10, 2018 at 01:10:01PM +0200, Michal Hocko wrote:
> >
> > Because do_brk does vma manipulations, for this reason it's
> > running under down_write_killable(>mmap_sem). Or you
> > mean something else?
>
> Yes, all we need the new lock for is to get a consistent view on brk
> values. I
Enable sensor after doing chipset specific initialization operation and
check sensor after doing chipset specific control operation.
Signed-off-by: Bartlomiej Zolnierkiewicz
---
drivers/thermal/samsung/exynos_tmu.c | 8 +---
1 file changed, 5 insertions(+), 3
Enable/check sensor after setting zone->tz and programming hwtrips.
Cc: Thierry Reding
Cc: Jonathan Hunter
Signed-off-by: Bartlomiej Zolnierkiewicz
---
drivers/thermal/tegra/soctherm.c | 6 +++---
1 file changed, 3
Enable sensor after checking trip points (unipher_tm_enable_sensor()
enables IRQ so we need to toggle sensor before calling it) and check
sensor after doing chipset specific enable sensor operation.
Cc: Masahiro Yamada
Signed-off-by: Bartlomiej Zolnierkiewicz
* Enable/check sensor explicitly in rockchip_thermal_probe() (also
check sensor after doing chipset specific control operation).
* Remove superfluous second sensor enable/check attempt.
Cc: Heiko Stuebner
Signed-off-by: Bartlomiej Zolnierkiewicz
---
Enable sensor after setting sensor data and check sensor after
writing update interval.
Cc: Eduardo Valentin
Cc: Keerthy
Signed-off-by: Bartlomiej Zolnierkiewicz
---
drivers/thermal/ti-soc-thermal/ti-thermal-common.c | 6 --
Enable/check sensor after setting tsc->zone and checking ntrips.
Signed-off-by: Bartlomiej Zolnierkiewicz
---
drivers/thermal/rcar_gen3_thermal.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/thermal/rcar_gen3_thermal.c
Dmitry Vyukov wrote:
> On Tue, Apr 10, 2018 at 12:55 PM, Tetsuo Handa
> wrote:
> > Hello.
> >
> > Since syzbot is reporting so many hung up bug which involves /dev/loopX ,
> > is it possible to "temporarily" apply below patch for testing under syzbot
>
>
On Tue, 10 Apr 2018 09:13:11 -0400
Steven Rostedt wrote:
> Something like this:
Zhaoyang, would this work for you?
Then all you need to do is to:
echo 0 > /d/tracing/options/mem-reclaim
and then you have the old behavior before Joel's patch. It will use
NORETRY and also
On Fri 2018-04-06 15:12:03, Rasmus Villemoes wrote:
> On 2018-04-06 14:26, Petr Mladek wrote:
> > On Thu 2018-04-05 16:46:23, Rasmus Villemoes wrote:
> >> On 2018-04-04 10:58, Petr Mladek wrote:
> >>
> >>> diff --git a/lib/vsprintf.c b/lib/vsprintf.c
> >>> index 3551b7957d9e..1a080a75a825 100644
>
Hi.
10.04.2018 08:35, Oleksandr Natalenko wrote:
- does it reproduce _without_ hardened usercopy? (I would assume yes,
but you'd just not get any warning until the hangs started.) If it
does reproduce without hardened usercopy, then a new bisect run could
narrow the search even more.
Looks
On Tue 10-04-18 05:53:51, Matthew Wilcox wrote:
> From: Matthew Wilcox
>
> The page cache has used the mapping's GFP flags for allocating
> radix tree nodes for a long time. It took care to always mask off the
> __GFP_HIGHMEM flag, and masked off other flags in other
On Tue, 10 Apr 2018 09:38:12 +0200
Quentin Schulz wrote:
> Hi Jonathan and Eugen,
>
> On Fri, Mar 30, 2018 at 02:02:12PM +0100, Jonathan Cameron wrote:
> > On Tue, 27 Mar 2018 15:32:33 +0300
> > Eugen Hristev wrote:
> >
> > > Hello,
>
On Wed, Apr 04, 2018 at 09:52:04AM +0200, Lukasz Majewski wrote:
> The 'kiebackpeter' entry has been added to vendor-prefixes.txt to indicate
> products from Kieback & Peter GmbH.
>
> Signed-off-by: Lukasz Majewski
> ---
> Documentation/devicetree/bindings/vendor-prefixes.txt | 1
On Wed, Apr 04, 2018 at 09:00:24PM +0200, H. Nikolaus Schaller wrote:
> It is not completely obvious that these are required as
> some .dts files don't specify them.
>
> Signed-off-by: H. Nikolaus Schaller
> ---
> .../devicetree/bindings/gpio/gpio-pca953x.txt | 33
>
On 10.04.2018 16:21, Miroslav Benes wrote:
I think you're missing my point. This isn't about your patch set, per
se. It's really about our existing code. Today, our patch stack
doesn't follow real stack semantics, because patches in the middle might
be disabled. I see that as a problem.
On 04/10/2018 07:37 AM, Mike Galbraith wrote:
> On Tue, 2018-04-10 at 10:59 +0200, Ingo Molnar wrote:
>> * Mike Galbraith wrote:
>>
>>> Hi Ingo,
>>>
>>> FYI, my i4790 box reboots immediately.. or close enough to it that you
>>> see nothing at all before again meeting the bios
Hi,
I'm working on a little driver that wants to pretend to be a section of mmio so
it can intercept accesses, or intercept accesses to a page after it's been
mmaped in by a user space program. So far I haven't found a method that works.
I had been trying to allocate a page, and in the fault
On Mon, Apr 09, 2018 at 09:39:06PM +0200, Takashi Iwai wrote:
> On Mon, 09 Apr 2018 20:57:43 +0200,
> Pierre-Louis Bossart wrote:
> >
> > On 4/9/18 5:46 AM, Jia-Ju Bai wrote:
> > > broxton_audio_probe() is never called in atomic context.
> > > This function is only set as ".probe" in "struct
Hi Dongjiu Geng,
On 09/04/18 22:36, Dongjiu Geng wrote:
> This new IOCTL exports user-invisible states related to SError.
> Together with appropriate user space changes, it can inject
> SError with specified syndrome to guest by setup kvm_vcpu_events
> value.
> Also it can support live
Hi Dongjiu Geng,
On 09/04/18 22:36, Dongjiu Geng wrote:
> 1. Detect whether KVM can set set guest SError syndrome
> 2. Support to Set VSESR_EL2 and inject SError by user space.
> 3. Support live migration to keep SError pending state and VSESR_EL2 value.
> 4. ACPI 6.1 adds support for NOTIFY_SEI
The following changes since commit 0adb32858b0bddf4ada5f364a84ed60b196dbcda:
Linux 4.16 (2018-04-01 14:20:27 -0700)
are available in the Git repository at:
git://linux-c6x.org/git/projects/linux-c6x-upstreaming.git tags/for-linus
for you to fetch changes up to
Hi Dongjiu Geng,
On 09/04/18 22:36, Dongjiu Geng wrote:
> Before user space injects a SError, it needs to know whether it can
> specify the guest Exception Syndrome, so KVM should tell user space
> whether it has such capability.
(you could improve the commit message by briefly explaining
Colin Ian King wrote:
> The pointer ndev is being dereferenced before it is being null checked,
> hence there is a potential null pointer deference. Fix this by only
> dereferencing ndev after it has been null checked
>
> Detected by CoverityScan, CID#1467010
> > > I love this. Nice work!
Yes, it looks really good.
> > > As you and Petr discussed, it would be nice to get rid of some of the
> > > delays, and also the callback tests will be very important.
> >
> > I've got v2 WIP that minimizes the delays, cleans up build flags, and
> > adds a basic
On Wed, Apr 4, 2018 at 10:00 PM, H. Nikolaus Schaller
wrote:
> The of_device_table is missing the PCA_PCAL flag so the
> pcal6524 would be operated in tca6424 compatibility mode which
> does not handle the new interrupt mask registers.
>
Reported-by or Suggested-by?
>
> As far as I understand, all this seems correct to me.
Good. Thank you, Joe!
> You want to maintain the core files in drivers/i2c/
> but not any files in any of algos/, busses/, or muxes/.
More specific: I don't want get_maintainer.pl to print me as a
maintainer for these drivers. This gives
Hi Marek,
On Tue, Apr 10, 2018 at 4:37 PM, Marek Vasut wrote:
> On 04/10/2018 03:26 PM, Geert Uytterhoeven wrote:
>> On Mon, Apr 9, 2018 at 11:59 PM, Marek Vasut wrote:
>>> On 04/09/2018 02:25 PM, Geert Uytterhoeven wrote:
Currently
On 09/04/2018 22:08, David Rientjes wrote:
> On Mon, 9 Apr 2018, Christoph Hellwig wrote:
>
>>> -#ifdef __HAVE_ARCH_PTE_SPECIAL
>>> +#ifdef CONFIG_ARCH_HAS_PTE_SPECIAL
>>> # define HAVE_PTE_SPECIAL 1
>>> #else
>>> # define HAVE_PTE_SPECIAL 0
>>
>> I'd say kill this odd indirection and just use
Hi Thomas,
On 10/04/18 16:01, Thomas Petazzoni wrote:
> Hello Marc, Hello Stephen,
>
> On Tue, 21 Mar 2017 09:43:24 +, Marc Zyngier wrote:
>
>> The whole idea behind this GICD_SETSPI_NSR is to offer a way to signal
>> SPIs using memory transaction, even allowing level interrupts (in
>>
Hey Linus,
Here is the pull request for dmaengine updates for v4.17-rc1. Two new
drivers, updates to couple and off updates to many summarise this request.
Details below:
The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1b2:
Linux 4.16-rc1 (2018-02-11 15:04:29 -0800)
On Tue, 10 Apr 2018 09:19:26 -0600
Alex Williamson wrote:
> On Tue, 10 Apr 2018 16:18:59 +0800
> Yulei Zhang wrote:
>
> > Corresponding to the V4 migration patch set for vfio pci device,
> > this patch is to implement the new ioctl
On 10/04/2018 14:15, KarimAllah Ahmed wrote:
> So disable the VMX-preemption timer if MWAIT is exposed to the guest!
>
> Cc: Paolo Bonzini
> Cc: Radim Krčmář
> Cc: Thomas Gleixner
> Cc: Ingo Molnar
> Cc: H. Peter
Enable/check sensor after HW-block setup (if necessary) and setting
data->tz.
Cc: Eric Anholt
Cc: Stefan Wahren
Signed-off-by: Bartlomiej Zolnierkiewicz
---
drivers/thermal/broadcom/bcm2835_thermal.c | 6 +++---
1 file
Enable/check sensor after setting priv->thermal.
Cc: Markus Mayer
Cc: bcm-kernel-feedback-l...@broadcom.com
Signed-off-by: Bartlomiej Zolnierkiewicz
---
drivers/thermal/broadcom/brcmstb_thermal.c | 4 ++--
1 file changed, 2 insertions(+), 2
On Sun, Apr 08, 2018 at 07:49:25PM -0700, Matthew Wilcox wrote:
> @@ -2714,8 +2714,10 @@ static __always_inline void *slab_alloc_node(struct
> kmem_cache *s,
> stat(s, ALLOC_FASTPATH);
> }
>
> - if (unlikely(gfpflags & __GFP_ZERO) && object)
> -
Replace magic numbers by a well known define in order to make the code
human readable and also facilitate the code reusability.
Signed-off-by: Gustavo Pimentel
---
Change v1->v2:
- Nothing changed, just to follow the patch set version.
Change v2->v3:
- Nothing
Replaces lower into upper case characters in comments and debug printks.
This is an attempt to keep the messages coherent within the designware
driver.
Also fixed code style on dw_pcie_irq_domain_free function.
Signed-off-by: Gustavo Pimentel
---
Change v1->v2:
-
The patch set was made against the Bjorn's next branch.
Adds support Designware EP support.
Increases the maximum number of interrupts allowed for Designware IP
controller.
Does a code cleanup on Designware driver:
- Replaces magic numbers without a easy meaning by a well known define
that
Am Dienstag, 10. April 2018, 14:51:37 CEST schrieb Geert Uytterhoeven:
> The use of of_clk_get_parent_{count,name}() and of_clk_init() is not
> limited to clock providers.
>
> Hence move these helpers into their own header file, so callers that are
> not clock providers no longer have to include
Hi Yisheng,
Sorry, I think we missed your question here.
On Wed, Mar 28, 2018 at 3:12 PM Yisheng Xie wrote:
> Hi Vivek,
> On 2018/3/28 12:37, Vivek Gautam wrote:
> > Hi Yisheng
> >
> >
> > On 3/28/2018 6:54 AM, Yisheng Xie wrote:
> >> Hi Vivek,
> >>
> >> On 2018/3/13
Quoting Colin King (2018-04-10 13:33:12)
> From: Colin Ian King
>
> The error exit path when a duplicate is found does not kfree and cmd_entry
> struct and hence there is a small memory leak. Fix this by kfree'ing it.
>
> Detected by CoverityScan, CID#1370198
Hi Marek,
On Mon, Apr 9, 2018 at 11:59 PM, Marek Vasut wrote:
> On 04/09/2018 02:25 PM, Geert Uytterhoeven wrote:
>> Currently add_mtd_device() failures are plainly ignored, which may lead
>> to kernel crashes later.
>> Fix this by ignoring and freeing partitions that
From: Bjorn Helgaas
pcibios_finish_adding_to_bus() is defined but never used. Remove it.
Signed-off-by: Bjorn Helgaas
---
arch/microblaze/include/asm/pci.h |2 --
arch/microblaze/pci/pci-common.c | 24
2 files changed,
On Mon, Apr 9, 2018 at 9:37 AM, Mikko Perttunen wrote:
>
>
> On 04/09/2018 04:21 PM, Rob Herring wrote:
>>
>> On Mon, Apr 9, 2018 at 12:38 AM, Mikko Perttunen wrote:
>>>
>>> Rob,
>>
>>
>> Please don't top post to lists.
>>
>>> this binding is for a specific IP
* Pavel Machek [180410 11:11]:
> Should the modem respond to AT commands on ttyS0? I launched minicom
> (115200 8N1) and I'm not getting any responses.
Not that I know. At least I never got anything out of it. But who knows,
maybe it is in normal mode initially during boot or when
On 04/10/2018 06:30 AM, Rob Herring wrote:
On Mon, Apr 9, 2018 at 9:37 AM, Mikko Perttunen wrote:
On 04/09/2018 04:21 PM, Rob Herring wrote:
On Mon, Apr 9, 2018 at 12:38 AM, Mikko Perttunen wrote:
Rob,
Please don't top post to lists.
this binding
On Mon, Apr 09, 2018 at 09:39:06PM +0200, Takashi Iwai wrote:
> It must be sleepable context as it's a standard platform driver probe
> callback.
> And now looking at grep output, only sound/soc/intel contains so many
> calls with GFP_ATOMIC. I bet that almost all can be done with
> GFP_KERNEL,
On Tue, 10 Apr 2018, Vlastimil Babka wrote:
> cache_reap() is initially scheduled in start_cpu_timer() via
> schedule_delayed_work_on(). But then the next iterations are scheduled via
> schedule_delayed_work(), thus using WORK_CPU_UNBOUND.
That is a bug.. cache_reap must run on the same cpu
sbni_probe1() is never called in atomic context.
The call chains ending up at sbni_probe1() are:
[1] sbni_probe1() <- sbni_init() <- sbni_probe() <- net_olddevs_init()
[2] sbni_probe1() <- sbni_isa_probe() <- sbni_init() <-
sbni_probe() <- net_olddevs_init()
[3] sbni_probe1() <-
On Tue, Apr 10, 2018 at 02:41:23PM +0100, Colin King wrote:
> From: Colin Ian King
>
> Currently function __load_ucode_amd can assign an uninitialized cp to *ret
> if get_builtin_microcode returns false.
What are you looking at? Here is how it looks in linux-next:
Colin Ian King wrote:
> Trivial fix to spelling mistake in message text
>
> Signed-off-by: Colin Ian King
> Signed-off-by: Kalle Valo
Patch applied to ath-next branch of ath.git, thanks.
6ce36faeac35 ath10k: fix
On Wed, Apr 4, 2018 at 10:00 PM, H. Nikolaus Schaller
wrote:
> in driver code. Therefore, the pca953x driver rejects the
> setup of the irq because it can only handle EDGE interrupts
> so far.
>
> This hack translates level interrupts to edge interrupts
> for the pca953x
On 04/10/2018 03:26 PM, Geert Uytterhoeven wrote:
> Hi Marek,
>
> On Mon, Apr 9, 2018 at 11:59 PM, Marek Vasut wrote:
>> On 04/09/2018 02:25 PM, Geert Uytterhoeven wrote:
>>> Currently add_mtd_device() failures are plainly ignored, which may lead
>>> to kernel crashes
Hi,
On Mon, Apr 9, 2018 at 11:36 PM, Manu Gautam wrote:
> Hi,
>
>
> On 3/30/2018 2:24 AM, Doug Anderson wrote:
>> Hi,
>>
>> On Thu, Mar 29, 2018 at 11:44 AM, Doug Anderson
>> wrote:
>>> Hi,
>>>
>>> On Thu, Mar 29, 2018 at 4:04 AM, Manu Gautam
Add a few livepatch modules and simple target modules that the included
regression suite can run tests against.
Signed-off-by: Joe Lawrence
---
Documentation/livepatch/callbacks.txt | 487 -
lib/Kconfig.debug
Round two cleans up a few misc script and build items, adds a shadow
variable test, and reduces the total livepatch kselftest runtime to ~45
seconds.
The tests run on top of Petr's v11 atomic replace feature and v2 of the
shadow variable enhancement patchsets:
[PATCH 0/8] livepatch: Atomic
An ADC is often used to measure other quantities indirectly. These
bindings describe two cases, a current through a shunt resistor, and
a "big" voltage measured with the help of a voltage divider.
Signed-off-by: Peter Rosin
---
.../bindings/iio/afe/current-sense-shunt.txt
If an ADC channel measures the midpoint of a voltage divider, the
interesting voltage is often the voltage over the full resistance.
E.g. if the full voltage is too big for the ADC to handle.
Likewise, if an ADC channel measures the voltage across a shunt
resistor, the interesting value is often
Hi!
This driver implements support for voltage dividers and current
sense shunts. It's pretty generic and should be easily adaptable
to other linear scaling purposes.
Cheers,
Peter
Changes since v2:https://lkml.org/lkml/2018/4/3/461
- Rename from current-sence-circuit to current-sense-shunt
On Tue, Apr 10, 2018 at 02:07:32PM +0200, Thomas Gleixner wrote:
> On Tue, 10 Apr 2018, Peter Zijlstra wrote:
> > Do you have any actual evidence for that? Is there a compiler stupid
> > enough to generate code to convert a bool to a 1bit value?
>
> Sure, if you do:
>
> > > > > > > + bool
Signed-off-by: Anders Roxell
---
tools/testing/selftests/bpf/.gitignore | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tools/testing/selftests/bpf/.gitignore
b/tools/testing/selftests/bpf/.gitignore
index 9cf83f895d98..5e1ab2f0eb79 100644
---
dm_TXPowerTrackingCallback_TSSI() is never called in atomic context.
dm_TXPowerTrackingCallback_TSSI() is only called by
dm_txpower_trackingcallback(), which is set a parameter of
INIT_DELAYED_WORK() in rtl8192_init_priv_task().
Despite never getting called from atomic context,
rtl8192_usb_disconnect() is never called in atomic context.
rtl8192_usb_disconnect() is only set as ".disconnect" in
struct usb_driver.
Despite never getting called from atomic context,
rtl8192_usb_disconnect() calls mdelay() to busily wait.
This is not necessary and can be replaced with
ieee80211_softmac_init() is never called in atomic context.
The call chains ending up at ieee80211_softmac_init() is:
[1] ieee80211_softmac_init() <- alloc_ieee80211_rsl() <-
rtl8192_usb_probe()
rtl8192_usb_probe() is set as ".probe" in struct usb_driver.
Despite never getting called from
ieee80211_tkip_init() is never called in atomic context.
ieee80211_tkip_init() is only set as ".init" in
struct ieee80211_crypto_ops.
The call chains ending up at "->init" function are:
[1] ->init() <- ieee80211_wpa_set_encryption() <-
ieee80211_wpa_supplicant_ioctl()
[2] ->init() <-
ieee80211_ccmp_init() is never called in atomic context.
ieee80211_ccmp_init() is only set as ".init" in
struct ieee80211_crypto_ops.
The call chains ending up at "->init" function are:
[1] ->init() <- ieee80211_wpa_set_encryption() <-
ieee80211_wpa_supplicant_ioctl()
[2] ->init() <-
prism2_wep_init() is never called in atomic context.
prism2_wep_init() is only set as ".init" in
struct ieee80211_crypto_ops.
The call chains ending up at "->init" function are:
[1] ->init() <- ieee80211_wpa_set_encryption() <-
ieee80211_wpa_supplicant_ioctl()
[2] ->init() <-
On Tue 10-04-18 05:05:28, Matthew Wilcox wrote:
> On Tue, Apr 10, 2018 at 10:26:43AM +0200, Michal Hocko wrote:
> > On Mon 09-04-18 12:40:44, Matthew Wilcox wrote:
> > > The problem is that the mapping gfp flags are used not only for allocating
> > > pages, but also for allocating the page cache
On Tue, 2018-04-10 at 09:00 +, Winkler, Tomas wrote:
> >
> > On Sat, 2018-04-07 at 19:12 +0300, Tomas Winkler wrote:
> > > In crb_map_io() function, __crb_request_locality() is called prior to
> > > crb_cmd_ready(), but if one of the consecutive function fails the flow
> > > bails out instead
On Tue, Apr 10, 2018 at 10:00:01AM +0200, Rafael J. Wysocki wrote:
> On Tue, Apr 10, 2018 at 9:33 AM, wrote:
> > +++ b/kernel/time/tick-sched.h
> > @@ -48,8 +48,8 @@ struct tick_sched {
> > unsigned long check_clocks;
> > enum
The PCIe controller dual mode is capable of operating in host mode as well
as endpoint mode by configuration, therefore this patch aims to add
endpoint mode support to the designware driver.
Signed-off-by: Gustavo Pimentel
---
Change v1->v2:
- Removed
The PCIe controller dual mode is capable of operating in host mode as well
as endpoint mode by configuration.
Signed-off-by: Gustavo Pimentel
---
Change v1->v2:
- Register new device id following Kishon's suggestion.
Change v2->v3:
- Nothing changed, just to follow
Adds a callback that defines the maximum number of vectors that can be use
by the Root Complex.
Since this is a parameter associated to each SoC IP setting, makes sense to
be configurable and easily visible to future modifications.
The designware IP supports a maximum of 256 vectors.
intel_scu_ipc_i2c_cntrl() calls mutex_lock(), which indicates
this function is not called in atomic context.
Despite never getting called from atomic context,
intel_scu_ipc_i2c_cntrl() calls mdelay to busily wait.
This is not necessary and can be replaced with usleep_range to
avoid busy waiting.
On Tue, Apr 10, 2018 at 05:53:50AM -0700, Matthew Wilcox wrote:
> From: Matthew Wilcox
>
> __GFP_ZERO requests that the object be initialised to all-zeroes,
> while the purpose of a constructor is to initialise an object to a
> particular pattern. We cannot do both. Add
Adds the designware EP device ID entry to pci_endpoint_test driver table
to allow this device to be recognize and handle by the pci_endpoint_test
driver.
Signed-off-by: Gustavo Pimentel
---
Change v1->v2:
- Changed device id following Kishon's suggestion.
Change
On Tue, Apr 03, 2018 at 08:09:08PM +0200, Peter Rosin wrote:
> On 2018-04-03 19:41, Andrew F. Davis wrote:
> > On 04/03/2018 10:36 AM, Peter Rosin wrote:
> >> Hi!
> >>
> >> This driver implements support for voltage dividers and current
> >> sense circuits. It's pretty generic and should be easily
On Tue, Apr 10, 2018 at 2:57 PM, Benjamin Herrenschmidt
wrote:
> On Tue, 2018-04-10 at 13:29 +0200, Arnd Bergmann wrote:
>> In the cases where an ad-hoc interface is needed, I can see
>> two options: we can stick something in drivers/soc that exposes
>> it in the least
On Tue, Apr 10, 2018 at 05:53:51AM -0700, Matthew Wilcox wrote:
> From: Matthew Wilcox
>
> The page cache has used the mapping's GFP flags for allocating
> radix tree nodes for a long time. It took care to always mask off the
> __GFP_HIGHMEM flag, and masked off other
On Tue 10-04-18 05:53:50, Matthew Wilcox wrote:
> From: Matthew Wilcox
>
> __GFP_ZERO requests that the object be initialised to all-zeroes,
> while the purpose of a constructor is to initialise an object to a
> particular pattern. We cannot do both. Add a warning to
On Mon, Apr 09, 2018 at 09:34:00AM +0200, Vincent Guittot wrote:
> Hi Morten,
>
> On 6 April 2018 at 14:58, Morten Rasmussen wrote:
> > On Thu, Apr 05, 2018 at 06:22:48PM +0200, Vincent Guittot wrote:
> >> Hi Morten,
> >>
> >> On 5 April 2018 at 17:46, Morten Rasmussen
zd1201_probe() is never called in atomic context.
zd1201_probe() is only set as ".probe" in struct usb_driver.
Despite never getting called from atomic context, zd1201_probe()
calls mdelay() to busily wait.
This is not necessary and can be replaced with msleep() to
avoid busy waiting.
This is
On Tue, Apr 10, 2018 at 01:26:30PM +0800, Stefan Hajnoczi wrote:
> Currently vhost *_access_ok() functions return int. This is error-prone
> because there are two popular conventions:
>
> 1. 0 means failure, 1 means success
> 2. -errno means failure, 0 means success
>
> Although vhost mostly
On 04/10/2018 05:53 AM, Matthew Wilcox wrote:
> From: Matthew Wilcox
>
> __GFP_ZERO requests that the object be initialised to all-zeroes,
> while the purpose of a constructor is to initialise an object to a
> particular pattern. We cannot do both. Add a warning to
On Wed, Apr 04, 2018 at 11:17:12AM +0300, Stefan Popa wrote:
> This patch adds basic support for Analog Devices I2C programmable linear
> battery charger.
>
> With this driver, some parameters can be read and configured such as:
> * trickle charge current level
> * trickle charge voltage
* Pavel Machek [180410 11:00]:
> On Mon 2018-04-09 07:08:47, Tony Lindgren wrote:
> > * Dan Williams [180408 02:46]:
> > > On Sat, 2018-04-07 at 14:22 +0200, Pavel Machek wrote:
> > > > I tried --location-enable-gps-unmanaged , but that did not work for
> > > > me.
Hi Rob,
> On Tue, Apr 03, 2018 at 06:59:45PM +0200, Lukasz Majewski wrote:
> > This commit adds device tree description of Kieback & Peter GmbH
> > iMX6Q TPC board.
> >
> > Signed-off-by: Lukasz Majewski
> >
> > ---
> > Changes for v2:
> > - SDPX license identifiers used
> > -
On 2018-04-10 07:06 PM, Thomas Gleixner wrote:
On Tue, 10 Apr 2018, yuank...@codeaurora.org wrote:
On 2018-04-10 05:10 PM, Thomas Gleixner wrote:
> On Tue, 10 Apr 2018, yuank...@codeaurora.org wrote:
> > On 2018-04-10 04:00 PM, Rafael J. Wysocki wrote:
> > > On Tue, Apr 10, 2018 at 9:33 AM,
> Am 10.04.2018 um 15:55 schrieb Rob Herring :
>
> On Wed, Apr 04, 2018 at 09:00:23PM +0200, H. Nikolaus Schaller wrote:
>> So let's describe this property in the bindings.
>
> It's not what the driver for some OS has. The h/w has a Vcc supply, so
> let's add a property for
On Tue, 10 Apr 2018, Jia-Ju Bai wrote:
> init_freecom() is never called in atomic context.
>
> init_freecom() is set as ".initFunction" through UNUSUAL_DEV().
> And ->initFunction() is only called by usb_stor_acquire_resources(),
> which is only called by usb_stor_probe2().
> usb_stor_probe2()
Hi Rob,
On 10 April 2018 07:24 Phil Edworthy wrote:
> On 09 April 2018 20:20 Rob Herring wrote:
> > On Wed, Mar 28, 2018 at 03:22:30PM +0100, Phil Edworthy wrote:
[...]
> > > +- interrupt-mask : a 32-bit bit mask that specifies which interrupts
> > > +in the list
> > > + of interrupts is valid,
Hi,
> Generally we try to cache mappings as much as possible. And wrt finding a
> slot: Create a sufficiently sized BAR on the virgl device, just for that?
Well. virtio has no concept of "bars" ...
The most common virtio transport layer happens to be pci, which actually
has bars. But we
Arnd Bergmann wrote:
> The way that 'strncat' is used here raised a warning in gcc-8:
>
> drivers/net/wireless/ath/ath10k/wmi.c: In function
> 'ath10k_wmi_tpc_stats_final_disp_tables':
> drivers/net/wireless/ath/ath10k/wmi.c:4649:4: error: 'strncat' output
> truncated before
201 - 300 of 2606 matches
Mail list logo