On Tue, Oct 08, 2019 at 05:25:17PM +0300, Dan Carpenter wrote:
> On Tue, Oct 08, 2019 at 04:21:54PM +0200, Matteo Croce wrote:
> > On Tue, Oct 8, 2019 at 3:16 PM Dan Carpenter
> > wrote:
> > >
> > > The subject doesn't match the patch. It should just be "remove useless
> > > printk".
> > >
> >
Quoting Cheng-yi Chiang (2019-10-07 11:50:31)
> On Mon, Oct 7, 2019 at 11:35 PM Stephen Boyd wrote:
> >
> > Quoting Cheng-yi Chiang (2019-10-07 06:58:41)
> > >
> > > Hi Guenter,
> > > Thanks for the quick review.
> > > I'll update accordingly in v2.
> >
> > I'd prefer this use the nvmem framework
On Tue, Oct 08, 2019 at 09:36:16AM +0200, Arnd Bergmann wrote:
> The compat_ptr_ioctl() infrastructure did not make it into
> linux-5.4, so cpwd now fails to build.
>
> Fix it by using an open-coded version.
>
> Fixes: 68f28b01fb9e ("watchdog: cpwd: use generic compat_ptr_ioctl")
>
On 10/8/19 7:55 AM, Alan Maguire wrote:
> Making kunit itself buildable as a module allows for "always-on"
> kunit configuration; specifying CONFIG_KUNIT=m means the module
> is built but only used when loaded. Kunit test modules will load
> kunit.ko as an implicit dependency, so simply running
>
Michael Kelley writes:
> From: Vitaly Kuznetsov Sent: Friday, October 4, 2019
> 9:57 AM
>>
>> Andrea Parri writes:
>>
>> > If the hardware supports TSC scaling, Hyper-V will set bit 15 of the
>> > HV_PARTITION_PRIVILEGE_MASK in guest VMs with a compatible Hyper-V
>> > configuration version.
On Tue, Oct 08, 2019 at 09:42:47AM +, Jerome Pouiller wrote:
> From: Jérôme Pouiller
>
> Most of problems are related to big-endian architectures.
kbuild still reports 2 errors with these patches applied:
Regressions in current branch:
drivers/staging/wfx/hif_tx.c:82:2-8: preceding lock
On Mon, Oct 07, 2019 at 05:41:10PM +, Dexuan Cui wrote:
> > From: linux-hyperv-ow...@vger.kernel.org
> > On Behalf Of Andrea Parri
> > Sent: Monday, October 7, 2019 9:31 AM
> >
> > Hi all,
> >
> > The patchset:
> >
> > - simplifies/refactors the VMBus negotiation code by introducing
> >
On Mon, 07 Oct 2019 10:17:16 +0200
Peter Zijlstra wrote:
> Ftrace was one of the last W^X violators; these patches move it over to the
> generic text_poke() interface and thereby get rid of this oddity.
>
Ingo, Thomas or H.Peter,
If it's OK with you, can you ack this series so that I can pull
Saurav Girepunje writes:
> Use the new helper that wraps the calls to platform_get_resource()
> and devm_ioremap_resource() together in dwc3_meson_g12a_probe().
>
> Signed-off-by: Saurav Girepunje
Reviewed-by: Kevin Hilman
> ---
> drivers/usb/dwc3/dwc3-meson-g12a.c | 4 +---
> 1 file
Check quota type in early stage so we can avoid many
unncessary operations when the type is wrong.
Signed-off-by: Chengguang Xu
---
fs/quota/quota.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/fs/quota/quota.c b/fs/quota/quota.c
index cb13fb76dbee..5444d3c4d93f
On Tue, 8 Oct 2019 16:54:24 +0200
Borislav Petkov wrote:
> On Tue, Oct 08, 2019 at 04:48:34PM +0200, Peter Zijlstra wrote:
> > Can, but why? That's more lines for no raisin ;-)
>
> Here's a raisin: I was looking at this and then all of a sudden went:
> "W00t, why is this do_sync part of the
08.10.2019 16:24, Bartlomiej Zolnierkiewicz пишет:
>
> On 10/8/19 2:47 PM, Mark Brown wrote:
>> On Tue, Oct 08, 2019 at 02:38:55PM +0200, Marek Szyprowski wrote:
>>
>>> Then if I get it right, the issue is caused by the commit 7f93ff73f7c8
>>> ("opp: core: add regulators enable and disable").
Hi Mason,
masonccy...@mxic.com.tw wrote on Tue, 8 Oct 2019 10:33:11 +0800:
> Hi Miquel,
>
> > >
> > > > Macronix AC series support using SET/GET_FEATURES to change
> > > > Block Protection and Unprotection.
> > > >
> > > > MTD default _lock/_unlock function replacement by manufacturer
> > >
/snip
> > > > > diff --git a/include/drm/drm_panel.h b/include/drm/drm_panel.h
> > > > > index d16158deacdc..f3587a54b8ac 100644
> > > > > --- a/include/drm/drm_panel.h
> > > > > +++ b/include/drm/drm_panel.h
> > > > > @@ -141,6 +141,56 @@ struct drm_panel {
> > > > >*/
> > > > >
as tests are added to kunit, it will become less feasible to execute
all built tests together. By supporting modular tests we provide
a simple way to do selective execution on a running system; specifying
CONFIG_KUNIT=y
CONFIG_KUNIT_EXAMPLE_TEST=m
...means we can simply "insmod example-test.ko"
Documentation should describe how to build kunit and tests as
modules.
Signed-off-by: Alan Maguire
Signed-off-by: Knut Omang
---
Documentation/dev-tools/kunit/faq.rst | 3 ++-
Documentation/dev-tools/kunit/index.rst | 3 +++
Documentation/dev-tools/kunit/usage.rst | 16
3
The current kunit execution model is to provide base kunit functionality
and tests built-in to the kernel. The aim of this series is to allow
building kunit itself and tests as modules. This in turn allows a
simple form of selective execution; load the module you wish to test.
In doing so, kunit
On Tue, Oct 08, 2019 at 06:35:11AM -0700, Sean Christopherson wrote:
> Hmm, I get assembler errors using gcc 5.4.0
Crap. 8.3 eats this just fine. And I guess we can accomodate old gccs
by having BIT() evaluate the enclosing UL() macro into its __ASSEMBLY__
variant but it ain't worth the trouble.
Making kunit itself buildable as a module allows for "always-on"
kunit configuration; specifying CONFIG_KUNIT=m means the module
is built but only used when loaded. Kunit test modules will load
kunit.ko as an implicit dependency, so simply running
"modprobe my-kunit-tests" will load the tests
On Mon, Oct 07, 2019 at 03:12:00PM -0700, dbasehore . wrote:
> On Mon, Oct 7, 2019 at 9:38 AM Sean Paul wrote:
> >
> > On Wed, Sep 25, 2019 at 03:58:30PM -0700, Derek Basehore wrote:
> > > This adds a helper function for reading the rotation (panel
> > > orientation) from the device tree.
> > >
>
Commit 204c91eff798a ("KVM: selftests: do not blindly clobber registers in
guest asm") was intended to make test more gcc-proof, however, the result
is exactly the opposite: on newer gccs (e.g. 8.2.1) the test breaks with
Test Assertion Failure
x86_64/sync_regs_test.c:168:
On 19-10-08 13:51, Mark Brown wrote:
> On Tue, Oct 08, 2019 at 08:03:11AM +0200, Marco Felsch wrote:
> > On 19-10-07 19:29, Mark Brown wrote:
> > > On Mon, Oct 07, 2019 at 11:34:29AM +0200, Marco Felsch wrote:
>
> > > > Sorry that won't fix my problem. If I drop the regulator-boot-on state
> > >
On Tue, Oct 08, 2019 at 03:43:51PM +0100, Alan Maguire wrote:
> Making kunit itself buildable as a module allows for "always-on"
> kunit configuration; specifying CONFIG_KUNIT=m means the module
> is built but only used when loaded. Kunit test modules will load
> kunit.ko as an implicit
On Tue 08-10-19 17:44:37, Kirill A. Shutemov wrote:
> On Mon, Oct 07, 2019 at 04:30:30PM +0200, Michal Hocko wrote:
> > On Mon 07-10-19 16:19:59, Vlastimil Babka wrote:
> > > On 10/2/19 10:43 AM, Michal Hocko wrote:
> > > > On Wed 02-10-19 06:16:43, Yang Shi wrote:
> > > >> The commit
On Tue, Oct 08, 2019 at 04:48:34PM +0200, Peter Zijlstra wrote:
> Can, but why? That's more lines for no raisin ;-)
Here's a raisin: I was looking at this and then all of a sudden went:
"W00t, why is this do_sync part of the loop at all? Do they belong
together? Nope."
If we're going to save on
Greetings My Dear Friend,
Before I introduce myself, I wish to inform you that this letter is not a hoax
mail and I urge you to treat it serious.This letter must come to you as a big
surprise, but I believe it is only a day that people meet and become great
friends and business partners.
On 08.10.19 16:36, lantianyu1...@gmail.com wrote:
> From: Tianyu Lan
>
> If size of offline memory region passed to offline_pages() is
> not aligned with PAGES_PER_SECTION, memory section will be set
> to offline in the offline_mem_sections() with some pages of
> memory section online. Fix it,
On Tue, Oct 08, 2019 at 10:40:10AM -0400, Steven Rostedt wrote:
> Seeing OPCODE_JMP32 and INSN_SIZE_JMP32 doesn't look like they are
> related to me.
But if it starts with OPCODE_ you know what it is - an opcode.
JMP32_INSN_OPCODE can first be shortened to JMP32_OPCODE and then having
instruction
On Tue, Oct 08, 2019 at 04:29:24PM +0200, Borislav Petkov wrote:
> On Mon, Oct 07, 2019 at 10:17:17AM +0200, Peter Zijlstra wrote:
> > @@ -63,8 +66,17 @@ static inline void int3_emulate_jmp(stru
> > regs->ip = ip;
> > }
> >
> > -#define INT3_INSN_SIZE 1
> > -#define CALL_INSN_SIZE 5
> >
as tests are added to kunit, it will become less feasible to execute
all built tests together. By supporting modular tests we provide
a simple way to do selective execution on a running system; specifying
CONFIG_KUNIT=y
CONFIG_KUNIT_EXAMPLE_TEST=m
...means we can simply "insmod example-test.ko"
Hello Tony,
On 10/8/19 4:23 PM, Tony Lindgren wrote:
> * Grygorii Strashko [191003 02:32]:
>> On 03/10/2019 11:16, Jeroen Hofstee wrote:
>>> Furthermore 4.19 is fine, so there is no need to include it in stable
>>> and have a note to make sure also other patches are required etc.
>> Hence all
For consumers wishing to run kunit on real hardware, it would be
ideal if the kunit framework and tests supported module-based builds.
This is an advantage as it reduces the test task to running
"modprobe mytests.ko", and CONFIG_KUNIT* options can be "always on"
(or rather "always m"). KUnit
On Tue, Oct 08, 2019 at 01:41:27PM +0200, Fabrice Gasnier wrote:
> Add a comment to better describe the purpose of breakinput feature that
> can be found on some STM32 timer instances. Briefly comment on the
> characteristics of this input for PWM, and pinmuxing as suggested in [1].
>
> [1]
Making kunit itself buildable as a module allows for "always-on"
kunit configuration; specifying CONFIG_KUNIT=m means the module
is built but only used when loaded. Kunit test modules will load
kunit.ko as an implicit dependency, so simply running
"modprobe my-kunit-tests" will load the tests
Documentation should describe how to build kunit and tests as
modules.
Signed-off-by: Knut Omang
Signed-off-by: Alan Maguire
---
Documentation/dev-tools/kunit/faq.rst | 3 ++-
Documentation/dev-tools/kunit/index.rst | 3 +++
Documentation/dev-tools/kunit/usage.rst | 16
3
On Mon, Oct 07, 2019 at 04:30:30PM +0200, Michal Hocko wrote:
> On Mon 07-10-19 16:19:59, Vlastimil Babka wrote:
> > On 10/2/19 10:43 AM, Michal Hocko wrote:
> > > On Wed 02-10-19 06:16:43, Yang Shi wrote:
> > >> The commit 87eaceb3faa59b9b4d940ec9554ce251325d83fe ("mm: thp: make
> > >> deferred
Jonathan,
Thanks for the review! I _think_ I've made all the changes you mentioned
locally. I'll run some more tests and clean it up a bit before submitting the
next patchset version.
> So my first thought was that Bosch have been moderately good at keeping their
> interfaces consistent across
On Mon, 07 Oct 2019 10:17:21 +0200
Peter Zijlstra wrote:
> Move ftrace over to using the generic x86 text_poke functions; this
> avoids having a second/different copy of that code around.
>
> This also avoids ftrace violating the (new) W^X rule and avoids
> fragmenting the kernel text
On Tue, 8 Oct 2019 16:29:24 +0200
Borislav Petkov wrote:
> On Mon, Oct 07, 2019 at 10:17:17AM +0200, Peter Zijlstra wrote:
> > In preparation for static_call and variable size jump_label support,
> > teach text_poke_bp() to emulate instructions, namely:
> >
> > JMP32, JMP8, CALL, NOP2,
Fix the following checkpatch errors:
$ ./scripts/checkpatch.pl --no-tree -f arch/mips/generic/init.c
ERROR: Use of const init definition must use __initconst
+static __initdata const void *fdt;
ERROR: Use of const init definition must use __initconst
+static __initdata const struct mips_machine
g - that masked the
> > original problem
>
> Right, I would definitely prefer to not make this built-in without a lot
> more information to *why* this is needed. In figuring that out, we'll
> probably find the race/timeout that's the root cause.
>
> Kevin
>
>
Kevin
On Tue, Oct 08, 2019 at 09:53:24AM -0400, Liang, Kan wrote:
>
>
> On 10/8/2019 4:31 AM, Peter Zijlstra wrote:
> > On Mon, Oct 07, 2019 at 10:59:01AM -0700, kan.li...@linux.intel.com wrote:
> > > diff --git a/include/linux/perf_event.h b/include/linux/perf_event.h
> > > index
From: Tianyu Lan
If size of offline memory region passed to offline_pages() is
not aligned with PAGES_PER_SECTION, memory section will be set
to offline in the offline_mem_sections() with some pages of
memory section online. Fix it, Update memory section status after
marking offline pages as
Hello Enric,
On Tue, Oct 08, 2019 at 12:54:17PM +0200, Enric Balletbo i Serra wrote:
> @@ -117,17 +122,28 @@ static void cros_ec_pwm_get_state(struct pwm_chip
> *chip, struct pwm_device *pwm,
> struct cros_ec_pwm_device *ec_pwm = pwm_to_cros_ec_pwm(chip);
> int ret;
>
> - ret =
On 08/10/2019 15:16, Peter Zijlstra wrote:
> On Wed, Oct 02, 2019 at 11:47:59AM +0100, Valentin Schneider wrote:
>
>> Yeah, right shift on signed negative values are implementation defined.
>
> Seriously? Even under -fno-strict-overflow? There is a perfectly
> sensible operation for signed shift
We must return a mask covering the full physical RAM when bypassing the
IOMMU mapping. Also, in iommu_need_mapping, we need to check using
dma_direct_get_required_mask to ensure that the device's dma_mask can
cover physical RAM before deciding to bypass IOMMU mapping.
Fixes: 249baa547901
Hi Vincent,
On Thu, Sep 19, 2019 at 09:33:31AM +0200 Vincent Guittot wrote:
> Several wrong task placement have been raised with the current load
> balance algorithm but their fixes are not always straight forward and
> end up with using biased values to force migrations. A cleanup and rework
>
On Tue, Oct 08, 2019 at 12:58:57PM +, Justin He (Arm Technology China)
wrote:
> Hi Will
>
> > -Original Message-
> > From: Will Deacon
> > Sent: 2019年10月8日 20:40
> > To: Justin He (Arm Technology China)
> > Cc: Catalin Marinas ; Mark Rutland
> > ; James Morse ; Marc
> > Zyngier ;
* Sebastian Reichel [191003 06:42]:
> Hi,
>
> This moves the remaining users of btwilink to the "new" serdev based hci_ll
> driver and drops the btwilink driver afterwards. The patches were only compile
> tested by me, but Enric tested the IGEP platform and Adam will test the
> LogicPD
>
Hi,
On 08/10/2019 16:25:41+0200, Michal Simek wrote:
> From: Srinivas Goud
>
> This patch fixes the warnings reported by static code analysis.
> Updated calibval variable type to unsigned type from signed.
>
> Signed-off-by: Srinivas Goud
> Signed-off-by: Michal Simek
> ---
>
>
On Tue, Oct 08, 2019 at 01:52:40PM +0200, Jiri Olsa wrote:
> On Mon, Oct 07, 2019 at 10:41:20AM -0700, Andi Kleen wrote:
> > From: Andi Kleen
> >
> > The symbol the feature file checks for is now actually in -lbabeltrace,
> > not -lbabeltrace-ctf, at least as of libbabeltrace-1.5.6-2.fc30.x86_64
On Mon, Oct 07, 2019 at 10:17:17AM +0200, Peter Zijlstra wrote:
> In preparation for static_call and variable size jump_label support,
> teach text_poke_bp() to emulate instructions, namely:
>
> JMP32, JMP8, CALL, NOP2, NOP_ATOMIC5, INT3
>
> The current text_poke_bp() takes a @handler argument
There is no reason to show error message if clocks are not ready yet.
Signed-off-by: Michal Simek
---
drivers/watchdog/cadence_wdt.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/watchdog/cadence_wdt.c b/drivers/watchdog/cadence_wdt.c
index
On Tue, Oct 08, 2019 at 04:21:54PM +0200, Matteo Croce wrote:
> On Tue, Oct 8, 2019 at 3:16 PM Dan Carpenter wrote:
> >
> > The subject doesn't match the patch. It should just be "remove useless
> > printk".
> >
> > regards,
> > dan carpenter
> >
>
> Well, it avoids leaking an address by
Hello Eric,
>>> Creating of a mount namespace in a user namespace automatically does
>>> 'mount("", "/", MS_SLAVE | MS_REC, NULL);' if the starting mount
>>> namespace was not created in that user namespace. AKA creating
>>> a mount namespace in a user namespace does the unshare for you.
>>
>>
From: Srinivas Goud
This patch fixes the warnings reported by static code analysis.
Updated calibval variable type to unsigned type from signed.
Signed-off-by: Srinivas Goud
Signed-off-by: Michal Simek
---
drivers/rtc/rtc-zynqmp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
On Tue, Oct 08, 2019 at 04:20:35PM +0200, Andrea Parri wrote:
> On Mon, Oct 07, 2019 at 04:18:26PM +0200, Dmitry Vyukov wrote:
> > On Mon, Oct 7, 2019 at 4:14 PM Andrea Parri wrote:
> > >
> > > > > > static struct taskstats *taskstats_tgid_alloc(struct task_struct
> > > > > > *tsk)
> > > > > >
* Grygorii Strashko [191003 02:32]:
> On 03/10/2019 11:16, Jeroen Hofstee wrote:
> > Furthermore 4.19 is fine, so there is no need to include it in stable
> > and have a note to make sure also other patches are required etc.
>
> Hence all above patches went in 5.1 it would be correct to mention
Hi Xingyu,
On Sun, 2019-09-29 at 14:24 +0800, Xingyu Chen wrote:
> This patchset adds support for Meson-A1 SoC Reset Controller. A new struct
> meson_reset_param is introduced to describe the register differences between
> Meson-A1 and previous SoCs.
>
> Changes since v2 at [1]:
> - add comments
On Tue, Oct 8, 2019 at 3:16 PM Dan Carpenter wrote:
>
> The subject doesn't match the patch. It should just be "remove useless
> printk".
>
> regards,
> dan carpenter
>
Well, it avoids leaking an address by removing an useless printk.
It seems that GKH already picked the patch in his staging
On Thu, Oct 3, 2019 at 7:06 AM Andrew Morton wrote:
>
> On Mon, 23 Sep 2019 20:27:25 +0800 Pengfei Li wrote:
>
> > Changes in v6
> > --
> > 1. abandon patch 4-7 (Because there is not enough reason to explain
> > that they are beneficial)
>
> So
On Mon, Oct 07, 2019 at 04:18:26PM +0200, Dmitry Vyukov wrote:
> On Mon, Oct 7, 2019 at 4:14 PM Andrea Parri wrote:
> >
> > > > > static struct taskstats *taskstats_tgid_alloc(struct task_struct
> > > > > *tsk)
> > > > > {
> > > > > struct signal_struct *sig = tsk->signal;
> > > > > -
On Tue, Oct 8, 2019 at 9:05 AM Rob Herring wrote:
>
> On Tue, Oct 8, 2019 at 7:50 AM Krzysztof Kozlowski wrote:
> >
> > On Tue, Oct 08, 2019 at 07:38:14AM -0500, Rob Herring wrote:
> > > On Fri, Oct 4, 2019 at 10:14 AM Krzysztof Kozlowski
> > > wrote:
> > > >
> > > > The clkoutN names of
* Graeme Smecher [191004 23:53]:
> Hi Andrey,
>
> On 2019-10-03 6:45 p.m., Andrey Smirnov wrote:
> > According to
> > Documentation/devicetree/bindings/i2c/i2c-mux-pca954x.txt,
> > i2c-mux-idle-disconnect is a property of a parent node since it
> > pertains to the mux/switch as a whole, so move
On Wed, Oct 02, 2019 at 11:47:59AM +0100, Valentin Schneider wrote:
> Yeah, right shift on signed negative values are implementation defined.
Seriously? Even under -fno-strict-overflow? There is a perfectly
sensible operation for signed shift right, this stuff should not be
undefined.
On Wed, Oct 02, 2019 at 06:43:09PM -0700, paul...@kernel.org wrote:
> From: "Paul E. McKenney"
>
> This commit replaces the use of rcu_swap_protected() with the more
> intuitively appealing rcu_replace() as a step towards removing
> rcu_swap_protected().
>
> Link:
>
It could happen that either `val` or `val2` [provided from userspace] is
negative. In that case the computed frequency could get a weird value.
Fix this by checking that neither of the 2 variables is negative, and check
that the computed result is not-zero.
Fixes: e4f959390178 ("iio: imu:
The linux-next commit
"hugetlb-remove-unused-hstate-in-hugetlb_fault_mutex_hash-fix" seems
accidentally add back an unused variable that was correctly removed in
the commit "hugetlb: remove unused hstate in hugetlb_fault_mutex_hash()"
[1].
mm/userfaultfd.c: In function '__mcopy_atomic_hugetlb':
Add DCC earlycon support for early printks. The patch is useful for SoC
bringup where HW serial console is broken.
Signed-off-by: Michal Simek
---
I have this patch in Xilinx tree for quite a long time and it was develop
as preparation work for SoC bringup where jtag is functional and get
On 2019-10-08 15:53, Tomasz Figa wrote:
> On Tue, Oct 8, 2019 at 10:35 PM Tomasz Figa wrote:
>> On Tue, Oct 8, 2019 at 7:42 PM Tomasz Figa wrote:
>>> On Tue, Oct 8, 2019 at 3:31 PM Jonas Karlman wrote:
On 2019-10-08 07:27, Tomasz Figa wrote:
> Hi Ezequiel, Jonas,
>
> On Tue,
On Tue 08-10-19 10:03:01, Qian Cai wrote:
[..]
> I don't think there is "removing useful messages" in this patch. That one
> printk() in __offline_isolated_pages() basically as Michal mentioned it is
> that
> useful, but could be converted to printk_deferred() if anyone objected.
"remove from
pn532 devices support an autopoll command, that lets the chip
automatically poll for selected nfc technologies instead of manually
looping through every single nfc technology the user is interested in.
This is faster and less cpu and bus intensive than manually polling.
This adds this autopoll
This switches the pn532 UART phy driver from manually polling to the new
autopoll mechanism.
Cc: Johan Hovold
Signed-off-by: Lars Poeschel
---
Changes in v9:
- Rebased the patch series on v5.4-rc2
Changes in v6:
- Rebased the patch series on v5.3-rc5
drivers/nfc/pn533/uart.c | 2 +-
1 file
This adds the UART phy interface for the pn533 driver.
The pn533 driver can be used through UART interface this way.
It is implemented as a serdev device.
Cc: Johan Hovold
Cc: Claudiu Beznea
Cc: David Miller
Signed-off-by: Lars Poeschel
---
Changes in v9:
- Rebased the patch series on
This adds documentation about the uart phy to the pn532 binding doc. As
the filename "pn533-i2c.txt" is not appropriate any more, rename it to
the more general "pn532.txt".
This also documents the deprecation of the compatible strings ending
with "...-i2c".
Cc: Johan Hovold
Cc: Simon Horman
It is favourable to have one unified compatible string for devices that
have multiple interfaces. So this adds simply "pn532" as the devicetree
binding compatible string and makes a note that the old ones are
deprecated.
Cc: Johan Hovold
Cc: Simon Horman
Signed-off-by: Lars Poeschel
---
There is a problem in the initialisation and setup of the pn533: It
registers with nfc too early. It could happen, that it finished
registering with nfc and someone starts using it. But setup of the pn533
is not yet finished. Bad or at least unintended things could happen.
So I split out nfc
This adds hooks for dev_up and dev_down to the phy_ops. They are
optional.
The idea is to inform the phy driver when the nfc chip is really going
to be used. When it is not used, the phy driver can suspend it's
interface to the nfc chip to save some power. The nfc chip is considered
not in use
The purpose of this patch series is to add a uart phy driver to the
pn533 nfc driver.
It first changes the dt strings and docs. The dt compatible strings
need to change, because I would add "pn532-uart" to the already
existing "pn533-i2c" one. These two are now unified into just
"pn532". Then the
> On Oct 8, 2019, at 2:35 AM, Peter Zijlstra wrote:
>
> On Wed, Oct 02, 2019 at 11:43:17PM -0700, Song Liu wrote:
>> This is a rare corner case, but it does happen:
>>
>> In perf_rotate_context(), when the first cpu flexible event fail to
>> schedule, cpu_rotate is 1, while cpu_event is
On Tue, 2019-10-08 at 15:42 +0200, Petr Mladek wrote:
> On Tue 2019-10-08 09:23:52, Qian Cai wrote:
> > On Tue, 2019-10-08 at 09:13 -0400, Steven Rostedt wrote:
> > > On Tue, 8 Oct 2019 10:15:10 +0200
> > > Petr Mladek wrote:
> > >
> > > > There are basically three possibilities:
> > > >
> > >
On Tue, Oct 08, 2019 at 04:26:06PM +0300, Heikki Krogerus wrote:
> Adding description for the device_is_available member which
> was missing, and fixing the description of the member
> property_read_int_array.
Reviewed-by: Andy Shevchenko
>
> Signed-off-by: Heikki Krogerus
> ---
>
On Tue, Oct 08, 2019 at 03:59:23PM +0200, Hans de Goede wrote:
> Hi,
>
> On 08-10-2019 14:25, Heikki Krogerus wrote:
> > Hi Hans,
> >
> > Fixed the compiler warning in this version. No other changes.
> >
> > The original cover letter:
> >
> > That AXP288 extcon driver is the last that uses
On Tue 08-10-19 15:52:59, Christian Brauner wrote:
> On Tue, Oct 08, 2019 at 03:36:37PM +0200, Christian Kellner wrote:
> > From: Christian Kellner
> >
> > The fdinfo file for a process file descriptor already contains the
> > pid of the process in the callers namespaces. Additionally, if pid
>
Hi,
On 08-10-2019 14:25, Heikki Krogerus wrote:
Hi Hans,
Fixed the compiler warning in this version. No other changes.
The original cover letter:
That AXP288 extcon driver is the last that uses build-in connection
description. I'm replacing it with a code that finds the role mux
software
As platform_get_irq() now prints an error when the interrupt does not
exist, counting interrupts by looping until failure causes the printing
of scary messages like:
rk_iommu ff924000.iommu: IRQ index 1 not found
rk_iommu ff914000.iommu: IRQ index 1 not found
rk_iommu ff903f00.iommu: IRQ index
On Mon, Oct 07, 2019 at 12:42:31PM -0600, Tuowen Zhao wrote:
> Some BIOS erroneously specifies write-combining BAR for intel-lpss-pci
> in MTRR. This will cause the system to hang during boot. If possible,
> this bug could be corrected with a firmware update.
>
> This patch adds devm_ioremap_uc
On 08/10/2019 13:45, Jonathan Cameron wrote:
> On Mon, 7 Oct 2019 10:07:22 -0700
> Hsin-Yi Wang wrote:
>
>> On Tue, Sep 10, 2019 at 12:59 AM Hsin-Yi Wang wrote:
>>>
>>> If devm_iio_channel_get() or devm_thermal_zone_of_sensor_register()
>>> fail with EPROBE_DEFER, we shouldn't print an error
On 2019-10-08 12:26, Tomasz Figa wrote:
> On Tue, Oct 8, 2019 at 3:23 PM Jonas Karlman wrote:
>> On 2019-10-08 05:29, Tomasz Figa wrote:
>>> Hi Jonas,
>>>
>>> On Tue, Oct 8, 2019 at 3:33 AM Jonas Karlman wrote:
On 2019-10-07 19:45, Ezequiel Garcia wrote:
> From: Francois Buergisser
On Tue, Oct 8, 2019 at 10:35 PM Tomasz Figa wrote:
>
> On Tue, Oct 8, 2019 at 7:42 PM Tomasz Figa wrote:
> >
> > On Tue, Oct 8, 2019 at 3:31 PM Jonas Karlman wrote:
> > >
> > > On 2019-10-08 07:27, Tomasz Figa wrote:
> > > > Hi Ezequiel, Jonas,
> > > >
> > > > On Tue, Oct 8, 2019 at 2:46 AM
On 10/8/2019 4:31 AM, Peter Zijlstra wrote:
On Mon, Oct 07, 2019 at 10:59:01AM -0700, kan.li...@linux.intel.com wrote:
diff --git a/include/linux/perf_event.h b/include/linux/perf_event.h
index 61448c19a132..ee9ef0c4cb08 100644
--- a/include/linux/perf_event.h
+++
On Tue, Oct 08, 2019 at 03:36:37PM +0200, Christian Kellner wrote:
> From: Christian Kellner
>
> The fdinfo file for a process file descriptor already contains the
> pid of the process in the callers namespaces. Additionally, if pid
> namespaces are configured, show the process ids of the
Commit 4294a779bd8d ("PM / devfreq: exynos-bus: Convert to use
dev_pm_opp_set_rate()") introduced errors:
exynos-bus: new bus device registered: soc:bus_wcore ( 84000 KHz ~ 40 KHz)
exynos-bus: new bus device registered: soc:bus_noc ( 67000 KHz ~ 10 KHz)
exynos-bus: new bus device
* Tero Kristo [191008 08:01]:
> On 07/10/2019 22:24, H. Nikolaus Schaller wrote:
> > Hi Tero,
> >
> > > Am 07.10.2019 um 21:18 schrieb Tero Kristo :
> > >
> > > On 07/10/2019 18:52, Tony Lindgren wrote:
> > > > Hi,
> > > > * H. Nikolaus Schaller [191005 16:59]:
> > > > Please try with Tero's
On Tue 08-10-19 15:42:56, Petr Mladek wrote:
[...]
> I am not -mm maintainer so I could not guarantee that a patch
> using printk_deferred() will get accepted. But it will have much
> bigger chance than the original patch.
I am not going to ack any such patch until it is clear what is the
actual
On 3/10/19 7:00 AM, Ramuthevar,Vadivel MuruganX wrote:
> From: Ramuthevar Vadivel Murugan
>
> The current arasan sdhci PHY configuration isn't compatible
> with the PHY on Intel's LGM(Lightning Mountain) SoC devices.
>
> Therefore, add a new compatible, to adapt the Intel's LGM
> SDXC PHY with
On 10/8/19 3:40 PM, Maxime Jourdan wrote:
> On 07/10/2019 18:39, Hans Verkuil wrote:
>> On 10/7/19 6:24 PM, Maxime Jourdan wrote:
>>> On 07/10/2019 17:12, Hans Verkuil wrote:
On 10/7/19 4:59 PM, Maxime Jourdan wrote:
> Hello,
>
> This patch series aims to bring H.264 support as
On Tue 2019-10-08 09:23:52, Qian Cai wrote:
> On Tue, 2019-10-08 at 09:13 -0400, Steven Rostedt wrote:
> > On Tue, 8 Oct 2019 10:15:10 +0200
> > Petr Mladek wrote:
> >
> > > There are basically three possibilities:
> > >
> > > 1. Do crazy exercises with locks all around the kernel to
> > >
Hi John, Peter,
On Tue, 2019-10-01 at 18:21 +, John Stultz wrote:
> From: Peter Griffin
>
> This is required to bring Mali450 gpu out of reset.
Do you know whether this is actually a module reset going to the GPU,
or if this is somehow part of the clock and power gating machinery?
There's
The linux-next commit "mm/z3fold.c: add inter-page compaction" [1]
introduced a few GCC compilation warnings.
mm/z3fold.c: In function 'compact_single_buddy':
mm/z3fold.c:693:16: warning: variable 'newpage' set but not used
[-Wunused-but-set-variable]
struct page *newpage;
401 - 500 of 925 matches
Mail list logo
