On Wed, 2019-10-02 at 21:14 -0700, Guenter Roeck wrote:
>
> On Tue, Sep 24, 2019 at 02:49:44PM +0200, Nuno Sá wrote:
> > The ltc2947 is a high precision power and energy monitor with an
> > internal sense resistor supporting up to +/- 30A. Three internal no
> > Latency ADCs ensure accurate measure
--git a/scripts/jobserver-count b/scripts/jobserver-count
> new file mode 100755
> index ..0b482d6884d2
> --- /dev/null
> +++ b/scripts/jobserver-count
> @@ -0,0 +1,58 @@
> +#!/usr/bin/env python
This breaks our daily linux-next build for an fedora 30 rpm on s3
On Thu, Oct 03, 2019 at 07:56:59PM -0700, Randy Dunlap wrote:
> Hi,
> Below are a few doc edits for you.
Thank you for the review! I'll fix the v2 according to your comments.
thanks,
--
heikki
On 25/09/2019 01.29, Kees Cook wrote:
>
> # User-friendly check for pdflatex and latexmk
> HAVE_PDFLATEX := $(shell if which $(PDFLATEX) >/dev/null 2>&1; then echo 1;
> else echo 0; fi)
> @@ -68,6 +68,7 @@ quiet_cmd_sphinx = SPHINX $@ --> file://$(abspath
> $(BUILDDIR)/$3/$4)
> PYTHOND
On Thu, Oct 03, 2019 at 12:12:07PM +0100, Julien Grall wrote:
> This patch fix an issue related to exposing the FRINT capability to
> userspace (see patch #1). The rest is documentation update.
>
For patches 2-4:
Acked-by: Will Deacon
Catalin can take them for 5.5, since I don't think they're ur
ipts/jobserver-count
>> @@ -0,0 +1,58 @@
>> +#!/usr/bin/env python
>
>
> This breaks our daily linux-next build for an fedora 30 rpm on s390x:
>
> + /usr/lib/rpm/redhat/brp-mangle-shebangs
> mangling shebang in
> /usr/src/kernels/5.4.0-20191004.rc1.git155.311ef88
From: Jeremy Linton
There are various reasons, such as benchmarking, to disable spectrev2
mitigation on a machine. Provide a command-line option to do so.
Signed-off-by: Jeremy Linton
Reviewed-by: Suzuki K Poulose
Reviewed-by: Andre Przywara
Reviewed-by: Catalin Marinas
Tested-by: Stefan Wah
On Wed, Oct 02, 2019 at 01:04:42PM +, Stefan-gabriel Mirea wrote:
> --- a/include/uapi/linux/serial_core.h
> +++ b/include/uapi/linux/serial_core.h
> @@ -290,7 +290,7 @@
> /* Sunix UART */
> #define PORT_SUNIX 121
>
> -/* Freescale Linflex UART */
> -#define PORT_LINFLEXUART 121
> +/*
Hello Greg,
On 10/4/2019 4:07 PM, gre...@linuxfoundation.org wrote:
> On Wed, Oct 02, 2019 at 01:04:42PM +, Stefan-gabriel Mirea wrote:
>> --- a/include/uapi/linux/serial_core.h
>> +++ b/include/uapi/linux/serial_core.h
>> @@ -290,7 +290,7 @@
>> /* Sunix UART */
>> #define PORT_SUNIX 121
>
On Mon, 23 Sep 2019, kbuild test robot wrote:
> Hi Thomas,
>
> I love your patch! Perhaps something to improve:
>
> [auto build test WARNING on linus/master]
> [cannot apply to v5.3 next-20190920]
> [if your patch is applied to the wrong git tree, please drop us a note to help
> improve the syst
> >drivers//mfd/ioc3.c: In function 'ioc3_eth_setup':
> > >> drivers//mfd/ioc3.c:281:54: warning: format '%llx' expects argument of
> > >> type 'long long unsigned int', but argument 4 has type 'resource_size_t
> > >> {aka unsigned int}' [-Wformat=]
> >sizeof(ioc3_w1_platform_data.dev
On Thu, 03 Oct 2019, Thomas Bogendoerfer wrote:
> SGI IOC3 chip has integrated ethernet, keyboard and mouse interface.
> It also supports connecting a SuperIO chip for serial and parallel
> interfaces. IOC3 is used inside various SGI systemboards and add-on
> cards with different equipped external
Hi All,
Here is v7 of my patch-set to add support for EFI embedded fw to the kernel.
v6 was posted a long time ago, around the 4.18 days. The long wait was for
a suitable secure-hash for checking the firmware we find embedded in the EFI
is the one we expect.
With 5.4-rc1 we finally have a standa
Just like with PCI options ROMs, which we save in the setup_efi_pci*
functions from arch/x86/boot/compressed/eboot.c, the EFI code / ROM itself
sometimes may contain data which is useful/necessary for peripheral drivers
to have access to.
Specifically the EFI code may contain an embedded copy of f
This is a preparation patch for adding a new platform fallback mechanism,
which will have its own enable/disable FW_OPT_xxx option.
Note this also fixes a typo in one of the re-wordwrapped comments:
enfoce -> enforce.
Signed-off-by: Hans de Goede
---
drivers/base/firmware_loader/fallback.c | 11
Sometimes it is useful to be able to dump the efi boot-services code and
data. This commit adds these as debugfs-blobs to /sys/kernel/debug/efi,
but only if efi=debug is passed on the kernel-commandline as this requires
not freeing those memory-regions, which costs 20+ MB of RAM.
Reviewed-by: Greg
In some cases the platform's main firmware (e.g. the UEFI fw) may contain
an embedded copy of device firmware which needs to be (re)loaded into the
peripheral. Normally such firmware would be part of linux-firmware, but in
some cases this is not feasible, for 2 reasons:
1) The firmware is customiz
Unfortunately sofar we have been unable to get permission to redistribute
Silead touchscreen firmwares in linux-firmware. This means that people
need to find and install the firmware themselves before the touchscreen
will work
Some UEFI/x86 tablets with a Silead touchscreen have a copy of the fw
e
Unfortunately sofar we have been unable to get permission to redistribute
icn8505 touchscreen firmwares in linux-firmware. This means that people
need to find and install the firmware themselves before the touchscreen
will work
Some UEFI/x86 tablets with an icn8505 touchscreen have a copy of the f
Add touchscreen info for the Chuwi Vi8 Plus tablet. This tablet uses a
Chipone ICN8505 touchscreen controller, with the firmware used by the
touchscreen embedded in the EFI firmware.
Acked-by: Andy Shevchenko
Acked-by: Ard Biesheuvel
Signed-off-by: Hans de Goede
---
Changes in v7:
- Remove PROP
Sofar we have been unable to get permission from the vendors to put the
firmware for touchscreens listed in touchscreen_dmi in linux-firmware.
Some of the tablets with such a touchscreen have a touchscreen driver, and
thus a copy of the firmware, as part of their EFI code.
This commit adds the ne
Hi Rob,
Just wanted to clarify something which I don't know if is something I'm
doing wrong or if it is some issue.
On Wed, 2019-10-02 at 14:06 -0500, Rob Herring wrote:
>
> On Wed, Oct 2, 2019 at 10:09 AM Sa, Nuno wrote:
> > On Wed, 2019-10-02 at 09:19 -0500, Rob Herring wrote:
> > > On Tue, S
On Fri, Oct 04, 2019 at 07:45:07AM +, Sa, Nuno wrote:
[ ... ]
> > > +static int ltc2947_val_read(struct ltc2947_data *st, const u8 reg,
> > > + const u8 page, const size_t size, s64 *val)
> > > +{
> > > + int ret;
> > > + u64 __val = 0;
> > > +
> > > + mutex_lock(&st->lock);
On Fri, Oct 4, 2019 at 9:59 AM Sa, Nuno wrote:
>
> Hi Rob,
>
> Just wanted to clarify something which I don't know if is something I'm
> doing wrong or if it is some issue.
>
> On Wed, 2019-10-02 at 14:06 -0500, Rob Herring wrote:
> >
> > On Wed, Oct 2, 2019 at 10:09 AM Sa, Nuno wrote:
> > > On W
On Wed, Sep 04, 2019 at 02:11:19PM -0700, Saravana Kannan wrote:
> Add device-links to track functional dependencies between devices
> after they are created (but before they are probed) by looking at
> their common DT bindings like clocks, interconnects, etc.
>
> Having functional dependencies au
On Wed, Sep 11, 2019 at 03:29:25AM -0700, Stephen Boyd wrote:
> Quoting Saravana Kannan (2019-09-04 14:11:22)
> > Add device links after the devices are created (but before they are
> > probed) by looking at common DT bindings like clocks and
> > interconnects.
> >
> > Automatically adding device
On Fri, Oct 04, 2019 at 11:15:46AM +0200, Rasmus Villemoes wrote:
> On 25/09/2019 01.29, Kees Cook wrote:
> > +# Extract and prepare jobserver file descriptors from envirnoment.
> > +try:
> > + # Fetch the make environment options.
> > + flags = os.environ['MAKEFLAGS']
> > +
> > + # Look for
On Fri, Oct 04, 2019 at 11:37:22AM +0100, Will Deacon wrote:
> On Thu, Oct 03, 2019 at 12:12:07PM +0100, Julien Grall wrote:
> > This patch fix an issue related to exposing the FRINT capability to
> > userspace (see patch #1). The rest is documentation update.
> >
> For patches 2-4:
>
> Acked-by:
While checking the results of the :c:func: removal, I noticed that there
was no documentation for request_irq(), and request_threaded_irq() was not
mentioned at all. Add a kerneldoc comment for request_irq() and add
request_threaded_irq() to the list of functions.
Signed-off-by: Jonathan Corbet
Initially I started out just getting rid of :c:func: clutter, but then
noticed that request_irq() wasn't documented - I am guessing that got left
behind when request_threaded_irq() came in. The second patch fixes that up
as well.
Happy to carry this up or let it go through the IRQ tree, whichever
As of 5.3, the automarkup extension will do the right thing with function()
notation, so we don't need to clutter the text with :c:func: invocations.
So remove them.
Signed-off-by: Jonathan Corbet
---
Documentation/core-api/genericirq.rst | 50 +--
1 file changed, 25 inse
www.bu3sch.de has been unusable for several years, but the same
information is available on bues.ch.
Cc: Michael Buesch
Signed-off-by: Jonathan Neuschäfer
---
Documentation/driver-api/gpio/bt8xxgpio.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/driver-api
Let's declutter Documentation/driver-api a bit.
Signed-off-by: Jonathan Neuschäfer
---
Is this where we want to put documentation about specific GPIO
drivers/chips? Or perhaps under a subheading?
---
Documentation/driver-api/{ => gpio}/bt8xxgpio.rst | 0
Documentation/driver-api/gpio/index.rst
As of 5.3, the automarkup extension will do the right thing with function()
notation, so we don't need to clutter the text with :c:func: invocations.
So remove them.
Looking at the generated output reveals that we lack kerneldoc coverage for
much of this API, but that's a separate problem.
Signed
This makes the code snippet more readable.
Signed-off-by: Jonathan Neuschäfer
---
Documentation/driver-api/pti_intel_mid.rst | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Documentation/driver-api/pti_intel_mid.rst
b/Documentation/driver-api/pti_intel_mid.rst
index 20f1c
On Fri, Oct 04, 2019 at 10:58:22AM -0600, Jonathan Corbet wrote:
> As of 5.3, the automarkup extension will do the right thing with function()
> notation, so we don't need to clutter the text with :c:func: invocations.
> So remove them.
>
> Looking at the generated output reveals that we lack kern
On Fri, 4 Oct 2019 18:40:56 +0200
Jonathan Neuschäfer wrote:
> www.bu3sch.de has been unusable for several years, but the same
> information is available on bues.ch.
>
> Cc: Michael Buesch
> Signed-off-by: Jonathan Neuschäfer
> ---
> Documentation/driver-api/gpio/bt8xxgpio.rst | 2 +-
> 1 fi
On Fri, 4 Oct 2019 15:44:53 +0100
Lee Jones wrote:
> On Thu, 03 Oct 2019, Thomas Bogendoerfer wrote:
> > + if (mask & BIT(IOC3_IRQ_ETH_DOMAIN))
> > + /* if eth irq is enabled we need to check in eth irq regs */
>
> Nit: Comments should be expressive. Please expand all of the
> short
Em Fri, 4 Oct 2019 19:14:17 +0200
Michael Büsch escreveu:
> On Fri, 4 Oct 2019 18:40:56 +0200
> Jonathan Neuschäfer wrote:
>
> > www.bu3sch.de has been unusable for several years, but the same
> > information is available on bues.ch.
> >
> > Cc: Michael Buesch
> > Signed-off-by: Jonathan Neu
On Fri, Oct 04, 2019 at 10:39:54AM -0600, Jonathan Corbet wrote:
> To make the transition to the new model easier and prevent the breakage
> -of existing implementations, the :c:func:`__do_IRQ` super-handler is still
> +of existing implementations, the __do_IRQ() super-handler is still
> availabl
Hi Hans,
I love your patch! Yet something to improve:
[auto build test ERROR on efi/next]
[cannot apply to v5.4-rc1 next-20191004]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specif
Hi Hans,
I love your patch! Yet something to improve:
[auto build test ERROR on efi/next]
[cannot apply to v5.4-rc1 next-20191004]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specif
Hi Hans,
On Fri, Oct 04, 2019 at 04:50:52PM +0200, Hans de Goede wrote:
> In some cases the platform's main firmware (e.g. the UEFI fw) may contain
> an embedded copy of device firmware which needs to be (re)loaded into the
> peripheral. Normally such firmware would be part of linux-firmware, but
On Fri, Oct 4, 2019 at 8:37 AM Greg Kroah-Hartman
wrote:
>
> On Wed, Sep 11, 2019 at 03:29:25AM -0700, Stephen Boyd wrote:
> > Quoting Saravana Kannan (2019-09-04 14:11:22)
> > > Add device links after the devices are created (but before they are
> > > probed) by looking at common DT bindings like
Hi Hans,
I love your patch! Yet something to improve:
[auto build test ERROR on efi/next]
[cannot apply to v5.4-rc1 next-20191004]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specif
45 matches
Mail list logo
