Adding the devicetree binding for labibb regulator.
Signed-off-by: Nisha Kumari
---
.../bindings/regulator/qcom-labibb-regulator.txt | 57 ++
1 file changed, 57 insertions(+)
create mode 100644
Documentation/devicetree/bindings/regulator/qcom-labibb-regulator.txt
diff --
This patch adds devicetree nodes for LAB and IBB regulators.
Signed-off-by: Nisha Kumari
---
arch/arm64/boot/dts/qcom/pmi8998.dtsi | 22 ++
1 file changed, 22 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/pmi8998.dtsi
b/arch/arm64/boot/dts/qcom/pmi8998.dtsi
index da32
This patch adds short circuit interrupt handling and recovery.
Signed-off-by: Nisha Kumari
---
drivers/regulator/qcom-labibb-regulator.c | 161 ++
1 file changed, 161 insertions(+)
diff --git a/drivers/regulator/qcom-labibb-regulator.c
b/drivers/regulator/qcom-labib
This patch adds labibb regulator driver for supporting LCD mode display
on SDM845 platform.
Signed-off-by: Nisha Kumari
---
drivers/regulator/Kconfig | 10 +
drivers/regulator/Makefile| 1 +
drivers/regulator/qcom-labibb-regulator.c | 438 ++
Em Wed, 12 Jun 2019 10:19:29 +0200
Wolfram Sang escreveu:
> On Tue, Jun 11, 2019 at 10:25:28AM +1000, Stephen Rothwell wrote:
> > Hi Wolfram,
> >
> > After merging the i2c tree, today's linux-next build (x86_64 allmodconfig)
> > produced this warning:
> >
> > drivers/media/dvb-frontends/tua6100
On Tue, Jun 11, 2019 at 03:30:19PM -0700, Matthias Kaehlcke wrote:
> On Tue, Jun 11, 2019 at 09:55:30AM -0700, Brian Norris wrote:
> > On Tue, Jun 11, 2019 at 3:49 AM Daniel Thompson
> > wrote:
> > > This is a long standing flaw in the backlight interfaces. AFAIK generic
> > > userspaces end up wi
On buses like SlimBus and SoundWire which does not support
gather_writes yet in regmap, A bulk write on paged register
would be silently ignored after programming page.
This is because local variable 'ret' value in regmap_raw_write_impl()
gets reset to 0 once page register is written successfully a
Hi Mauro,
> That entire use of _P, _R and _ri looks weird into my eyes. The code there
Yes.
> do things like:
>
> #define _P 32
>
> ...
>
> if (_P == 64)
> reg1[1] |= 0x40;
Yup, I saw this, too, but didn't feel like refactoring the driver.
Thanks for stepping up!
> I
On 6/12/2019 12:10 PM, Ulf Hansson wrote:
drivers/net/wireless/broadcom/brcm80211/brcmfmac/bcmsdh.c:
mmc_set_data_timeout(md, func->card);
mmc_wait_for_req(func->card->host, mr);
These are not okay, none of these things calls should really be done
from an SDIO func driver.
It tells me tha
On Tue, 11 Jun 2019, YueHaibing wrote:
> In module_add_modinfo_attrs if sysfs_create_file
> fails, we forget to free allocated modinfo_attrs
> and roll back the sysfs files.
>
> Fixes: 03e88ae1b13d ("[PATCH] fix module sysfs files reference counting")
> Signed-off-by: YueHaibing
Reviewed-by: Mi
Hi,
This patchset is fixing several issues reported by checkpatch but also
major number handling for multiple allocated ports. For more information
please look at the first patch which describes more details.
When this patchset is applied driver only reports one checkpatch warning
which should be
From: Shubhrajyoti Datta
Let kernel to find out major number dynamically for the first device and
then reuse it for other instances.
This fixes the issue that each uart is registered with a
different major number.
After the patch:
crw---1 root root 253, 0 Jun 10 08:31 /dev/tty
On Tue, Jun 11, 2019 at 7:50 PM Catalin Marinas wrote:
>
> On Tue, Jun 11, 2019 at 07:18:04PM +0200, Andrey Konovalov wrote:
> > On Tue, Jun 11, 2019 at 5:01 PM Catalin Marinas
> > wrote:
> > > static void *tag_ptr(void *ptr)
> > > {
> > > static int tagged_addr_err = 1;
> > > un
From: Nava kishore Manne
Trivial patch which fixes one checkpatch warning:
WARNING: line over 80 characters
+ !(readl(port->membase + CDNS_UART_SR)
& CDNS_UART_SR_TXFULL)) {
Fixes: c8dbdc842d30 ("serial: xuartps: Rewrite the interrupt handling logic")
From: Nava kishore Manne
Trivial patch which fixes this checkpatch warning:
WARNING: Avoid multiple line dereference - prefer 'port->state->xmit.tail'
+ port->state->xmit.buf[port->state->xmit.
+ tail], port->membase + CDNS_UART_FIFO);
From: Nava kishore Manne
This patch fixes this checkpatch warning:
WARNING: macros should not use a trailing semicolon
+#define to_cdns_uart(_nb) container_of(_nb, struct cdns_uart, \
+ clk_rate_change_nb);
Fixes: d9bb3fb12685 ("tty: xuartps: Rebrand driver as Cadence UART")
Signed
From: Nava kishore Manne
There is no reason to call return at the end of function which should
return void.
The patch is also remove one checkpatch warning:
WARNING: void function return statements are not generally useful
+ return;
+}
Fixes: 6ee04c6c5488 ("tty: xuartps: Add polled mode s
From: Nava kishore Manne
Octal permission is preffered compare to symbolic one.
This patch fixes checkpatch warnings:
Symbolic permissions 'S_IRUGO' are not preferred. Consider using octal
permissions '0444'.
Fixes: 85baf542d54e ("tty: xuartps: support 64 byte FIFO size")
Signed-off-by: Nava ki
From: Boris Brezillon
Date: Wed, Jun 12, 2019 at 07:15:33
> On Tue, 11 Jun 2019 16:06:43 +0200
> Vitor Soares wrote:
>
> > Currently the I3C framework limits SCL frequency to FM speed when
> > dealing with a mixed slow bus, even if all I2C devices are FM+ capable.
> >
> > The core was also not
Hi.
On Tue, Jun 4, 2019 at 2:49 AM Alexey Brodkin
wrote:
>
> Hi Vineet,
>
> > -Original Message-
> > From: Vineet Gupta
> > Sent: Monday, June 3, 2019 7:25 PM
> > To: Alexey Brodkin ;
> > linux-snps-...@lists.infradead.org
> > Cc: linux-kernel@vger.kernel.org; Masahiro Yamada
> >
> >
On Wed, Jun 12, 2019 at 12:59:45PM +0200, Pavel Machek wrote:
> > - Problem
> >
> > Naturally, cached apps were dominant consumers of memory on the system.
> > However, they were not significant consumers of swap even though they are
> > good candidate for swap. Under investigation, swapping out o
On Tue, 11 Jun 2019 18:29:49 +0100,
Marc Zyngier wrote:
>
> On 11/06/2019 17:59, Lorenzo Pieralisi wrote:
> > On Fri, Apr 12, 2019 at 08:35:36AM +, Z.q. Hou wrote:
> >> From: Hou Zhiqiang
> >>
> >> The current code does not support multiple MSIs, so remove
> >> the corresponding flag from th
These are used nowhere in the tree (except for some architectures which
define them for their own use) and were already removed in:
commit 6474924e2b5d ("arch: remove unused macro/function thread_saved_pc()")
commit c17c02040bf0 ("arch: remove unused *_segments() macros/functions")
Remove them fr
As reported by Stephen:
> After merging the i2c tree, today's linux-next build (x86_64 allmodconfig)
> produced this warning:
>
> drivers/media/dvb-frontends/tua6100.c: In function 'tua6100_set_params':
> drivers/media/dvb-frontends/tua6100.c:71: warning: "_P" redefined
> #define _P 32
>
> In fil
Hi Eugen,
On Wed, Jun 12, 2019 at 11:01:15AM +, eugen.hris...@microchip.com wrote:
> From: Eugen Hristev
>
> Fixed issues that can lead to potential bugs.
> Cleanup order in the driver
> Taking into consideration std control creation can fail
> mutex_destroy call
> changing controller_format
Schöne Grüße!!
Als erstes, möchte ich Ihnen um Ihre vertrauen in diese Transaktion bitten,
diese ist völlig vertraulich und streng Geheim. Doch ich weiß dass, die
Transaktion auf diese Größe, jeder besorgt und beunruhigt machen kann, aber ich
versichere Ihnen, das am Ende alles gut laufen wird.
Friendly ping...
Thanks,
Gao Xiang
On 2019/6/3 17:13, Gao Xiang wrote:
> non-inline io_schedule() was introduced in
> commit 10ab56434f2f ("sched/core: Separate out io_schedule_prepare() and
> io_schedule_finish()")
> Keep in line with io_schedule_timeout, Otherwise
> "/proc//wchan" will report
On Tue, Jun 11, 2019 at 07:36:36PM +, Nadav Amit wrote:
> Please change the title of the patch to “vmw_balloon” (it is currently
> “vmw_ballon”).
Oops, will fix, sorry about that.
> > On Jun 11, 2019, at 11:55 AM, Greg Kroah-Hartman
> > wrote:
> >
> > When calling debugfs functions, there
Hi Lorenzo,
Thanks a lot for your comments!
> -Original Message-
> From: Lorenzo Pieralisi
> Sent: 2019年6月12日 1:00
> To: Z.q. Hou
> Cc: linux-...@vger.kernel.org; linux-arm-ker...@lists.infradead.org;
> devicet...@vger.kernel.org; linux-kernel@vger.kernel.org;
> bhelg...@google.com; rob
On Tue, Jun 11, 2019 at 01:43:56PM -0700, Kees Cook wrote:
> On Tue, Jun 11, 2019 at 08:32:13PM +0200, Greg Kroah-Hartman wrote:
> > When calling debugfs functions, there is no need to ever check the
> > return value. The function can work or not, but the code logic should
> > never do something d
Hi Lorenzo,
Thanks a lot for your comments!
> -Original Message-
> From: Lorenzo Pieralisi
> Sent: 2019年6月12日 1:18
> To: Z.q. Hou ; bhelg...@google.com
> Cc: linux-...@vger.kernel.org; linux-arm-ker...@lists.infradead.org;
> devicet...@vger.kernel.org; linux-kernel@vger.kernel.org;
> rob
On Wed, 12 Jun 2019 11:16:34 +
Vitor Soares wrote:
> From: Boris Brezillon
> Date: Wed, Jun 12, 2019 at 07:15:33
>
> > On Tue, 11 Jun 2019 16:06:43 +0200
> > Vitor Soares wrote:
> >
> > > Currently the I3C framework limits SCL frequency to FM speed when
> > > dealing with a mixed slow b
Hi!
> > > This approach is similar in spirit to madvise(MADV_WONTNEED), but the
> > > information required to make the reclaim decision is not known to the app.
> > > Instead, it is known to a centralized userspace daemon, and that daemon
> > > must be able to initiate reclaim on its own without a
Em Wed, 12 Jun 2019 13:00:39 +0200
Borislav Petkov escreveu:
> On Wed, Jun 12, 2019 at 07:42:42AM -0300, Mauro Carvalho Chehab wrote:
> > That's said, from the admin PoV, it makes sense to have a single
> > daemon that collect errors from all error sources and take the
> > needed actions.
>
>
Stephen Smalley wrote:
> > (6) The security attributes of all the objects between the object in (5)
> > and the object in (4), assuming we work from (5) towards (4) if the
> > two aren't coincident (WATCH_INFO_RECURSIVE).
>
> Does this apply to anything other than mount notificatio
On Wed, Jun 12, 2019 at 12:29:17PM +0200, Jan Kara wrote:
> > > The main objection to the current ODP & DAX solution is that very
> > > little HW can actually implement it, having the alternative still
> > > require HW support doesn't seem like progress.
> > >
> > > I think we will eventually sta
On Wed, Jun 12, 2019 at 4:53 PM Christoph Hellwig wrote:
>
> On Wed, Jun 12, 2019 at 04:35:22PM +1000, Oliver O'Halloran wrote:
> > Setting a 48 bit DMA mask doesn't work today because we only allocate
> > IOMMU tables to cover the 0..2GB range of PCI bus addresses.
>
> I don't think that is true
Em Wed, 12 Jun 2019 13:09:04 +0200
Wolfram Sang escreveu:
> Hi Mauro,
>
> > That entire use of _P, _R and _ri looks weird into my eyes. The code there
>
> Yes.
>
> > do things like:
> >
> > #define _P 32
> >
> > ...
> >
> > if (_P == 64)
> > reg1[1] |= 0x40;
>
>
On Wed, 12 Jun 2019 at 13:11, Arend Van Spriel
wrote:
>
> On 6/12/2019 12:10 PM, Ulf Hansson wrote:
> >> drivers/net/wireless/broadcom/brcm80211/brcmfmac/bcmsdh.c:
> >>mmc_set_data_timeout(md, func->card);
> >>mmc_wait_for_req(func->card->host, mr);
> > These are not okay, none of these th
On Tue, 2019-04-30 at 20:58 +0200, Nicolas Saenz Julienne wrote:
> Some hardware configurations might pass on providing an interrupt line.
> In that case there is always the option to use a polled input approach.
> This patch adapts the driver for it.
>
> The polled approach is only triggered if n
On Wed, 2019-06-12 at 08:42 -0300, Mauro Carvalho Chehab wrote:
> > Yes, we do have different error reporting facilities but I still
> > think
> > that concentrating all the error information needed in order to do
> > proper recovery action is the better approach here. And make that
> > part
> > of
On Wed 2019-06-12 17:36:43, Sergey Senozhatsky wrote:
> On (06/06/19 09:10), Petr Mladek wrote:
> > Just to be sure. I wanted to say that I like the idea with
> > KERN_UNSUPRESSED. So, I think that we are on the same page.
>
> I understand. All I wanted to say is that KERN_UNSUPRESSED is
> per-mes
From: Eugen Hristev
Checkpatch complaining that locks do not have comments,
unaligned code and macro reuse of same argument in to_isc_clk.
Fixed them by renaming, realigning and adding struct comments
Signed-off-by: Eugen Hristev
Acked-by: Sakari Ailus
---
Changes in v5, v6:
- none
Changes i
From: Eugen Hristev
Fixed issues that can lead to potential bugs.
Cleanup order in the driver
Taking into consideration std control creation can fail
mutex_destroy call
changing controller_formats with const specifier
some cosmetic cleanups
Signed-off-by: Eugen Hristev
---
Changes in v6:
- adde
On Wed, Jun 12, 2019 at 08:25:03AM -0300, Mauro Carvalho Chehab wrote:
> As reported by Stephen:
>
> > After merging the i2c tree, today's linux-next build (x86_64 allmodconfig)
> > produced this warning:
> >
> > drivers/media/dvb-frontends/tua6100.c: In function 'tua6100_set_params':
> > drivers/
> > OK, so that means I should send my pull request after yours in the next
> > merge window? To avoid the build breakage?
>
> Either that or you can apply my patch on your tree before the
> patch that caused the breakage.
>
> Just let me know what works best for you.
Hmm, the offending patch
This patch fixes a spelling typo found in imx214.c
Signed-off-by: Masanari Iida
---
drivers/media/i2c/imx214.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/i2c/imx214.c b/drivers/media/i2c/imx214.c
index 83e9961b0505..159a3a604f0e 100644
--- a/drivers/media/i
On Wed 12-06-19 08:47:21, Jason Gunthorpe wrote:
> On Wed, Jun 12, 2019 at 12:29:17PM +0200, Jan Kara wrote:
>
> > > > The main objection to the current ODP & DAX solution is that very
> > > > little HW can actually implement it, having the alternative still
> > > > require HW support doesn't seem
The newly added evict callback shall be called by nsfs_evict(). Currently
only put() callback is called in nsfs_evict(), it is not able to release
all netns refcount, for example, a rpc client holds two netns refcounts,
these refcounts are supposed to be released when the rpc client is freed,
but t
This patch series fixes an auth_gss bug that results in netns refcount
leaks when use-gss-proxy is set to 1.
The problem was found in privileged docker containers with gssproxy service
enabled and /proc/net/rpc/use-gss-proxy set to 1, the corresponding
struct net->count ends up at 2 after containe
The newly added netns_evict() shall be called when the netns inode being
evicted. It provides another path to release netns refcounts, previously
netns_put() is the only choice, but it is not able to release all netns
refcount, for example, a rpc client holds two netns refcounts, these
refcounts ar
On Tue, Jun 11, 2019 at 4:10 PM Icenowy Zheng wrote:
> The pinctrl driver of V3s is already available and used in the kernel,
> but the compatible string of it is forgotten to be added.
>
> Add the missing compatible string.
>
> Signed-off-by: Icenowy Zheng
> Acked-by: Maxime Ripard
> Reviewed-
When use-gss-proxy is set to 1, write_gssp() creates a rpc client in
gssp_rpc_create(), this increases netns refcount by 2, these refcounts are
supposed to be released in rpcsec_gss_exit_net(), but it will never happen
because rpcsec_gss_exit_net() is triggered only when netns refcount gets
to 0, s
On Tue, Jun 11, 2019 at 4:11 PM Icenowy Zheng wrote:
> The Allwinner V3 SoC, despite come with the same die with V3s, has more
> GPIO pins than V3s, and a different compatible string for pinctrl is
> needed.
>
> Add the compatible string for V3 pinctrl.
>
> Signed-off-by: Icenowy Zheng
> Reviewe
When calling debugfs functions, there is no need to ever check the
return value. The function can work or not, but the code logic should
never do something different based on this.
Also, because there is no need to save the file dentry, remove the
variable that was saving it and just recursively
When calling debugfs functions, there is no need to ever check the
return value. The function can work or not, but the code logic should
never do something different based on this.
Cc: Rajneesh Bhardwaj
Cc: "David E. Box"
Cc: Darren Hart
Cc: Andy Shevchenko
Cc: platform-driver-...@vger.kernel
When calling debugfs functions, there is no need to ever check the
return value. The function can work or not, but the code logic should
never do something different based on this.
Cc: Rajneesh Bhardwaj
Cc: Vishwanath Somayaji
Cc: Darren Hart
Cc: Andy Shevchenko
Cc: platform-driver-...@vger.k
When calling debugfs functions, there is no need to ever check the
return value. The function can work or not, but the code logic should
never do something different based on this.
Cc: Darren Hart
Cc: Andy Shevchenko
Cc: platform-driver-...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Signe
When calling debugfs functions, there is no need to ever check the
return value. The function can work or not, but the code logic should
never do something different based on this.
Cc: Corentin Chary
Cc: Darren Hart
Cc: Andy Shevchenko
Cc: platform-driver-...@vger.kernel.org
Cc: linux-kernel@v
When calling debugfs functions, there is no need to ever check the
return value. The function can work or not, but the code logic should
never do something different based on this.
Cc: Matthew Garrett
Cc: "Pali Rohár"
Cc: Darren Hart
Cc: Andy Shevchenko
Cc: platform-driver-...@vger.kernel.org
When calling debugfs functions, there is no need to ever check the
return value. The function can work or not, but the code logic should
never do something different based on this.
Cc: Ike Panhc
Cc: Darren Hart
Cc: Andy Shevchenko
Cc: platform-driver-...@vger.kernel.org
Cc: linux-kernel@vger.k
When calling debugfs functions, there is no need to ever check the
return value. The function can work or not, but the code logic should
never do something different based on this.
Cc: Corentin Chary
Cc: Darren Hart
Cc: Andy Shevchenko
Cc: acpi4asus-u...@lists.sourceforge.net
Cc: platform-driv
On Tue, Jun 11, 2019 at 4:10 PM Icenowy Zheng wrote:
> dt-bindings: pinctrl: add missing compatible string for V3s
> dt-bindings: pinctrl: add compatible string for Allwinner V3 pinctrl
I applied these two so we get down the depth of the patch stack.
Waiting for a v3 on the pinctrl patch.
> Subject: Re: linux-next: Fixes tag needs some work in the imx-mxs tree
>
> On Tue, Jun 11, 2019 at 08:36:52AM +, Peng Fan wrote:
> > Hi Shawn, Stephen
> > > Subject: Re: linux-next: Fixes tag needs some work in the imx-mxs
> > > tree
> > >
> > > On Fri, Jun 07, 2019 at 07:46:52AM +1000, S
On Tue, Jun 11, 2019 at 9:20 AM Lubomir Rintel wrote:
> The original license text had a typo ("publishhed") which would be
> likely to confuse automated licensing auditing tools. Let's just switch
> to SPDX instead of fixing the wording.
>
> Signed-off-by: Lubomir Rintel
This is already fixed u
On Tue, Jun 11, 2019 at 9:20 AM Lubomir Rintel wrote:
> The original license text had a typo ("publishhed") which would be
> likely to confuse automated licensing auditing tools. Let's just switch
> to SPDX instead of fixing the wording.
>
> Signed-off-by: Lubomir Rintel
Already fixed upstream
On 06.06.2019 11:06, Igor Opaniuk wrote:
> From: Igor Opaniuk
>
> Allows to use the SD interface at a higher speed mode if the card
> supports it. For this the signaling voltage is switched from 3.3V to
> 1.8V under the usdhc1's drivers control.
>
> Signed-off-by: Igor Opaniuk
> ---
> arch/arm
Dave,
are you comfortable with me taking these patches
through the renesas tree? Or perhaps should they be reposted
to you for inclusion in net-next?
They have been stuck for a long time now.
On Fri, Jun 07, 2019 at 10:02:13AM +, Fabrizio Castro wrote:
> Dear All,
>
> These patches have bee
On Wednesday 12 June 2019 14:12:53 Greg Kroah-Hartman wrote:
> When calling debugfs functions, there is no need to ever check the
> return value. The function can work or not, but the code logic should
> never do something different based on this.
>
> Cc: Matthew Garrett
> Cc: "Pali Rohár"
> Cc
On Wed, Jun 12, 2019 at 10:11:58AM +0200, Anders Roxell wrote:
> When building with CONFIG_MFD_88PM800 and CONFIG_REGULATOR_88PM800
> enabled as loadable modules, we see the following warning:
Please use subject lines matching the style for the subsystem. This
makes it easier for people to identi
On Wed, Jun 12, 2019 at 11:18:25AM +0800, YueHaibing wrote:
> If CONFIG_I2C is m and CONFIG_I2C_SLAVE is y,
> building with CONFIG_IPMB_DEVICE_INTERFACE setting to
> y will fail:
Ok, I have added this to my linux-next tree.
-corey
>
> drivers/char/ipmi/ipmb_dev_int.o: In function `ipmb_remove':
On Tue, Jun 11, 2019 at 02:06:40PM +0100, Fabrizio Castro wrote:
> Document RZ/G2M (R8A774A1) SoC in the Renesas TMU bindings.
>
> Signed-off-by: Fabrizio Castro
Reviewed-by: Simon Horman
On Wed, Jun 12, 2019 at 09:57:40PM +1000, Benjamin Herrenschmidt wrote:
> On Wed, 2019-06-12 at 08:42 -0300, Mauro Carvalho Chehab wrote:
> > > Yes, we do have different error reporting facilities but I still
> > > think
> > > that concentrating all the error information needed in order to do
> > >
The w5X00 chip provides an SPI to Ethernet inteface. This patch allows
platform devices to be defined through the device tree.
Signed-off-by: Nicolas Saenz Julienne
---
drivers/net/ethernet/wiznet/w5100-spi.c | 24 ++--
1 file changed, 22 insertions(+), 2 deletions(-)
diff -
Commit-ID: 0e5aa23282f8e6ee38c18f67ddfdaaa32d3df86b
Gitweb: https://git.kernel.org/tip/0e5aa23282f8e6ee38c18f67ddfdaaa32d3df86b
Author: Yangtao Li
AuthorDate: Fri, 7 Jun 2019 13:42:53 -0400
Committer: Thomas Gleixner
CommitDate: Wed, 12 Jun 2019 10:21:17 +0200
hrtimer: Remove unused he
No need to check the return value of debugfs_create_file(), so no need
to provide a fake "cast away" of the return value either.
Cc: Dan Williams
Cc: Vinod Koul
Cc: dmaeng...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman
---
drivers/dma/amba-pl08x.c | 5 ++-
No need to check the return value of debugfs_create_file(), so no need
to provide a fake "cast away" of the return value either.
Cc: Linus Walleij
Cc: Vinod Koul
Cc: Dan Williams
Cc: linux-arm-ker...@lists.infradead.org
Cc: dmaeng...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Signed-off-b
When calling debugfs functions, there is no need to ever check the
return value. The function can work or not, but the code logic should
never do something different based on this.
Also, because there is no need to save the file dentry, remove the
variable that was saving it as it was never even
When calling debugfs functions, there is no need to ever check the
return value. The function can work or not, but the code logic should
never do something different based on this.
Also, because there is no need to save the file dentry, remove the
variables that were saving them as they were neve
Commit-ID: 87d3aa28f345bea77c396855fa5d5fec4c24461f
Gitweb: https://git.kernel.org/tip/87d3aa28f345bea77c396855fa5d5fec4c24461f
Author: James Morse
AuthorDate: Mon, 3 Jun 2019 18:25:31 +0100
Committer: Thomas Gleixner
CommitDate: Wed, 12 Jun 2019 10:31:50 +0200
x86/resctrl: Don't stop
When calling debugfs functions, there is no need to ever check the
return value. The function can work or not, but the code logic should
never do something different based on this.
Cc: Sudeep Dutt
Cc: Ashutosh Dixit
Cc: Dan Williams
Cc: Vinod Koul
Cc: dmaeng...@vger.kernel.org
Cc: linux-kerne
When calling debugfs functions, there is no need to ever check the
return value. The function can work or not, but the code logic should
never do something different based on this.
Also, because there is no need to save the file dentry, remove the
variable that was saving it as it was never even
Add bindings for Wiznet's w5x00 series of SPI interfaced Ethernet chips.
Based on the bindings for microchip,enc28j60.
Signed-off-by: Nicolas Saenz Julienne
---
Changes since v1:
- one compatible sting per line
- use correct 'ethenet@0' phandle name
.../devicetree/bindings/net/wiznet,w5x0
On Mon, Jun 10, 2019 at 4:18 PM Linus Walleij wrote:
> The FMC subsystem was created in 2012 with the ambition to
> drive development of drivers for this hardware upstream.
>
> The current implementation has architectural flaws and would
> need to be revamped using real hardware to something that
Commit-ID: c7563e62a6d720aa3b068e26ddffab5f0df29263
Gitweb: https://git.kernel.org/tip/c7563e62a6d720aa3b068e26ddffab5f0df29263
Author: Prarit Bhargava
AuthorDate: Mon, 10 Jun 2019 13:15:44 -0400
Committer: Thomas Gleixner
CommitDate: Wed, 12 Jun 2019 10:31:50 +0200
x86/resctrl: Preven
Commit-ID: 619c1baa91b2820eae9ff5d89eb525df81ea7a5a
Gitweb: https://git.kernel.org/tip/619c1baa91b2820eae9ff5d89eb525df81ea7a5a
Author: Daniel Lezcano
AuthorDate: Mon, 27 May 2019 22:55:14 +0200
Committer: Thomas Gleixner
CommitDate: Wed, 12 Jun 2019 10:47:03 +0200
genirq/timings: Fix
Commit-ID: 2840eef0513c518faeb8a0ab8d07268c6285cdd0
Gitweb: https://git.kernel.org/tip/2840eef0513c518faeb8a0ab8d07268c6285cdd0
Author: Daniel Lezcano
AuthorDate: Mon, 27 May 2019 22:55:15 +0200
Committer: Thomas Gleixner
CommitDate: Wed, 12 Jun 2019 10:47:03 +0200
genirq/timings: Fix
On Wed, Jun 12, 2019 at 11:44:35AM +0200, Jason A. Donenfeld wrote:
> Hey Peter,
>
> On Wed, Jun 12, 2019 at 11:03 AM Peter Zijlstra wrote:
> > How quasi? Do the comments in kernel/sched/clock.c look like something
> > you could use?
> >
> > As already mentioned in the other tasks, anything ktime
This patch fixes a spelling typo in rds.txt
Signed-off-by: Masanari Iida
---
Documentation/networking/rds.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/networking/rds.txt b/Documentation/networking/rds.txt
index 0235ae69af2a..f2a0147c933d 100644
--- a/Docu
Commit-ID: 3c2e79f4cef7938125b356e7f5c8fd038212619a
Gitweb: https://git.kernel.org/tip/3c2e79f4cef7938125b356e7f5c8fd038212619a
Author: Daniel Lezcano
AuthorDate: Mon, 27 May 2019 22:55:16 +0200
Committer: Thomas Gleixner
CommitDate: Wed, 12 Jun 2019 10:47:03 +0200
genirq/timings: Opti
Commit-ID: df025e47e4e34b779af2cc72c350877be7104ef3
Gitweb: https://git.kernel.org/tip/df025e47e4e34b779af2cc72c350877be7104ef3
Author: Daniel Lezcano
AuthorDate: Mon, 27 May 2019 22:55:17 +0200
Committer: Thomas Gleixner
CommitDate: Wed, 12 Jun 2019 10:47:04 +0200
genirq/timings: Enca
On 5/16/19 5:29 PM, Fabrice Gasnier wrote:
> During probe, return the "get_irq" error value instead of -EINVAL which
> allows the driver to be deferred probed if needed.
> Fix also the case where of_irq_get() returns a negative value.
> Note :
> On failure of_irq_get() returns 0 or a negative value
Commit-ID: 23aa3b9a6b7d5029c1f124426bc5ba4430dcc29c
Gitweb: https://git.kernel.org/tip/23aa3b9a6b7d5029c1f124426bc5ba4430dcc29c
Author: Daniel Lezcano
AuthorDate: Mon, 27 May 2019 22:55:18 +0200
Committer: Thomas Gleixner
CommitDate: Wed, 12 Jun 2019 10:47:04 +0200
genirq/timings: Enca
Commit-ID: 6aed82de719b424bd5548aa4179e95f34fd779ab
Gitweb: https://git.kernel.org/tip/6aed82de719b424bd5548aa4179e95f34fd779ab
Author: Daniel Lezcano
AuthorDate: Mon, 27 May 2019 22:55:19 +0200
Committer: Thomas Gleixner
CommitDate: Wed, 12 Jun 2019 10:47:04 +0200
genirq/timings: Add
Commit-ID: f52da98d900e18a250cb14ca426d4041ea7002db
Gitweb: https://git.kernel.org/tip/f52da98d900e18a250cb14ca426d4041ea7002db
Author: Daniel Lezcano
AuthorDate: Mon, 27 May 2019 22:55:20 +0200
Committer: Thomas Gleixner
CommitDate: Wed, 12 Jun 2019 10:47:05 +0200
genirq/timings: Add
Em Wed, 12 Jun 2019 14:04:39 +0200
Wolfram Sang escreveu:
> > > OK, so that means I should send my pull request after yours in the next
> > > merge window? To avoid the build breakage?
> >
> > Either that or you can apply my patch on your tree before the
> > patch that caused the breakage.
>
Commit-ID: 699785f5d898965408430e841d10cd1cb2c02a77
Gitweb: https://git.kernel.org/tip/699785f5d898965408430e841d10cd1cb2c02a77
Author: Daniel Lezcano
AuthorDate: Mon, 27 May 2019 22:55:21 +0200
Committer: Thomas Gleixner
CommitDate: Wed, 12 Jun 2019 10:47:05 +0200
genirq/timings: Add
Hi,
On 12-06-19 02:16, dbasehore . wrote:
On Tue, Jun 11, 2019 at 1:54 AM Hans de Goede wrote:
Hi,
On 11-06-19 10:08, Jani Nikula wrote:
On Mon, 10 Jun 2019, Derek Basehore wrote:
This removes the orientation quirk detection from the code to add
an orientation property to a panel. This is
Commit-ID: 0e51833042fccfe882ef3e85a346252550d26c22
Gitweb: https://git.kernel.org/tip/0e51833042fccfe882ef3e85a346252550d26c22
Author: Minwoo Im
AuthorDate: Sun, 2 Jun 2019 20:21:17 +0900
Committer: Thomas Gleixner
CommitDate: Wed, 12 Jun 2019 10:52:45 +0200
genirq/affinity: Remove un
Commit-ID: a66d955e910ab0e598d7a7450cbe6139f52befe7
Gitweb: https://git.kernel.org/tip/a66d955e910ab0e598d7a7450cbe6139f52befe7
Author: Pavankumar Kondeti
AuthorDate: Mon, 3 Jun 2019 10:01:03 +0530
Committer: Thomas Gleixner
CommitDate: Wed, 12 Jun 2019 11:03:05 +0200
cpu/hotplug: Abor
301 - 400 of 911 matches
Mail list logo
