Hello,
Alexandre GRIVEAUX wrote:
> Adding leds and related triggers.
Applied to mips-next.
> commit 24b0cb4f883a
> https://git.kernel.org/mips/c/24b0cb4f883a
>
> Signed-off-by: Alexandre GRIVEAUX
> Signed-off-by: Paul Burton
Thanks,
Paul
[ This message was auto-generated; if you believe
Hello,
Alexandre GRIVEAUX wrote:
> Add IW8103 Wifi + bluetooth module to device tree and related power domain.
Applied to mips-next.
> commit 948f2708f945
> https://git.kernel.org/mips/c/948f2708f945
>
> Signed-off-by: Alexandre GRIVEAUX
> Signed-off-by: Paul Burton
Thanks,
Paul
[ This
On Mon, Oct 07, 2019 at 09:34:48AM +0200, Christoph Hellwig wrote:
> Hi Arvind,
>
> can you try the patch below?
>
>
> diff --git a/drivers/iommu/intel-iommu.c b/drivers/iommu/intel-iommu.c
> index 3f974919d3bd..52b709bf2b55 100644
> --- a/drivers/iommu/intel-iommu.c
> +++ b/drivers/iommu/intel-
Since we link purgatory.ro with -r aka we enable "incremental linking"
no checks for unresolved symbols is done while linking purgatory.ro.
Changes to the sha256 code has caused the purgatory in 5.4-rc1 to have
a missing symbol on memzero_explicit, yet things still happily build.
This commit adds
On Mon, Oct 07, 2019 at 01:54:32PM -0400, Arvind Sankar wrote:
> It doesn't boot with the patch. Won't it go
> dma_get_required_mask
> -> intel_get_required_mask
> -> iommu_need_mapping
> -> dma_get_required_mask
> ?
>
> Should the call to dma_get_required_mask in iommu_nee
Add necessary compatible flag for HiSi's DWC3 so
dwc3-of-simple will probe.
Cc: Greg Kroah-Hartman
Cc: Felipe Balbi
Cc: Andy Shevchenko
Cc: Rob Herring
Cc: Mark Rutland
Cc: Yu Chen
Cc: Matthias Brugger
Cc: Chunfeng Yun
Cc: linux-...@vger.kernel.org
Cc: devicet...@vger.kernel.org
Signed-off
From: Yu Chen
A GCTL soft reset should be executed when switch mode for dwc3 core
of Hisilicon Kirin Soc.
Cc: Greg Kroah-Hartman
Cc: Felipe Balbi
Cc: Andy Shevchenko
Cc: Rob Herring
Cc: Mark Rutland
Cc: Yu Chen
Cc: Matthias Brugger
Cc: Chunfeng Yun
Cc: linux-...@vger.kernel.org
Cc: devic
I've been carrying for awhile some patches that Yu Chen was
previously pushing upstream to enable USB on the HiKey960 board
and I wanted to try to nudge them forward as I'm not sure as to
what his plans are.
This series is just the simpler parts of the patch set that I
wanted to send out to see if
From: Yu Chen
It needs more time for the device controller to clear the CmdAct of
DEPCMD on Hisilicon Kirin Soc.
Cc: Greg Kroah-Hartman
Cc: Felipe Balbi
Cc: Andy Shevchenko
Cc: Rob Herring
Cc: Mark Rutland
Cc: Yu Chen
Cc: Matthias Brugger
Cc: Chunfeng Yun
Cc: linux-...@vger.kernel.org
Cc
From: Yu Chen
This patch adds support for the poweron and shutdown of dwc3 core
on Hisilicon Soc Platform.
Cc: Greg Kroah-Hartman
Cc: Felipe Balbi
Cc: Andy Shevchenko
Cc: Rob Herring
Cc: Mark Rutland
Cc: Yu Chen
Cc: Matthias Brugger
Cc: Chunfeng Yun
Cc: linux-...@vger.kernel.org
Cc: devi
Provide a dt-binding for quirk needed to do a GCTL soft reset on mode
switching
Cc: Greg Kroah-Hartman
Cc: Felipe Balbi
Cc: Andy Shevchenko
Cc: Rob Herring
Cc: Mark Rutland
Cc: Yu Chen
Cc: Matthias Brugger
Cc: Chunfeng Yun
Cc: linux-...@vger.kernel.org
Cc: devicet...@vger.kernel.org
Signed
On Sat, Oct 05, 2019 at 06:44:08PM +0200, Borislav Petkov wrote:
> > +static struct sgx_epc_page *sgx_section_get_page(
>
> That fits into 80 cols (oh well, 81) and even if not, a trailing opening
> arg brace is ugly.
But checkpatch.pl will complain about it...
/Jarkko
On 07/10/2019 03:26, Paul E. McKenney wrote:
>
> On Fri, Oct 04, 2019 at 03:24:02PM -0700, Paul E. McKenney wrote:
>> On Fri, Oct 04, 2019 at 07:49:10PM +, Stefan Reiter wrote:
>>> Commit 18cd8c93e69e ("rcu/nocb: Print gp/cb kthread hierarchy if
>>> dump_tree") added print statements to rcu_or
On Mon, Oct 07, 2019 at 07:55:28PM +0200, Christoph Hellwig wrote:
> On Mon, Oct 07, 2019 at 01:54:32PM -0400, Arvind Sankar wrote:
> > It doesn't boot with the patch. Won't it go
> > dma_get_required_mask
> > -> intel_get_required_mask
> > -> iommu_need_mapping
> > -> dma_get_requi
On Mon, Oct 7, 2019 at 12:44 PM John Stultz wrote:
>
> On Tue, Jul 23, 2019 at 9:51 PM Vinod Koul wrote:
> >
> > We get a warning about missing unit name for soc node, so add it.
> >
> > arch/arm64/boot/dts/qcom/sdm845.dtsi:623.11-2814.4: Warning
> > (unit_address_vs_reg): /soc: node has a reg o
On Mon, Oct 07, 2019 at 10:56:30AM -0700, Christoph Hellwig wrote:
> On Mon, Oct 07, 2019 at 07:55:28PM +0200, Christoph Hellwig wrote:
> > On Mon, Oct 07, 2019 at 01:54:32PM -0400, Arvind Sankar wrote:
> > > It doesn't boot with the patch. Won't it go
> > > dma_get_required_mask
> > > -> intel
Hello,
Aurabindo Jayamohanan wrote:
> {save,restore}_dsp() internally checks if the cpu has dsp support.
> Therefore, explicit check is not required before calling them in
> {save,restore}_processor_state()
Applied to mips-next.
> commit 9662dd752c14
> https://git.kernel.org/mips/c/9662dd752c14
On Mon, Oct 07, 2019 at 04:11:53PM +0200, Ondřej Jirman wrote:
> Hi Maxime,
>
> On Fri, Aug 23, 2019 at 12:31:34PM +0200, megous hlavni wrote:
> > From: Ondrej Jirman
> >
> > (Resend to add missing lists, sorry for the noise.)
> >
> > This series implements bluetooth support for Xunlong Orange Pi
From: Kan Liang
In LBR call stack mode, the depth of reconstructed LBR call stack limits
to the number of LBR registers. With LBR Top-of-Stack (TOS) information,
perf tool may stitch the stacks of two samples. The reconstructed LBR
call stack can break the HW limitation.
Add a new sample type fo
From: Kan Liang
Start from Haswell, Linux perf can utilize the existing Last Branch
Record (LBR) facility to record call stack. However, the depth of the
reconstructed LBR call stack limits to the number of LBR registers.
E.g. on skylake, the depth of reconstructed LBR call stack is <= 32
That's
From: Kan Liang
In LBR call stack mode, the depth of reconstructed LBR call stack limits
to the number of LBR registers.
For example, on skylake, the depth of reconstructed LBR call stack is
always <= 32.
# To display the perf.data header info, please use
# --header/--header-only option
From: Kan Liang
With the LBR stitching approach, the reconstructed LBR call stack
can break the HW limitation. However, it may reconstruct invalid call
stacks in some cases, e.g. exception handing such as setjmp/longjmp.
Also, it may impact the processing time especially when the number of
sample
From: Kan Liang
To stitch LBR call stack, the max LBR information is required. So the
CPU PMU capabilities information has to be stored in perf header.
Add a new feature HEADER_CPU_PMU_CAPS for CPU PMU capabilities.
Retrieve all CPU PMU capabilities, not just max LBR information.
Add variable m
From: Kan Liang
With the LBR stitching approach, the reconstructed LBR call stack
can break the HW limitation. However, it may reconstruct invalid call
stacks in some cases, e.g. exception handing such as setjmp/longjmp.
Also, it may impact the processing time especially when the number of
sample
From: Kan Liang
With the LBR stitching approach, the reconstructed LBR call stack
can break the HW limitation. However, it may reconstruct invalid call
stacks in some cases, e.g. exception handing such as setjmp/longjmp.
Also, it may impact the processing time especially when the number of
sample
From: Kan Liang
With the LBR stitching approach, the reconstructed LBR call stack
can break the HW limitation. However, it may reconstruct invalid call
stacks in some cases, e.g. exception handing such as setjmp/longjmp.
Also, it may impact the processing time especially when the number of
sample
From: Kan Liang
The PMU capabilities information, which is located at
/sys/bus/event_source/devices//caps, is required by perf tool.
For example, the max LBR information is required to stitch LBR call
stack.
Add perf_pmu__caps_parse() to parse the PMU capabilities information.
The information is
From: Kan Liang
LBR only collect the user call stack. To reconstruct a call stack, both
kernel call stack and user call stack are required. The function
resolve_lbr_callchain_sample() mix the kernel call stack and user
call stack. Now, with the help of TOS, perf tool can reconstruct a more
comple
From: Kan Liang
Support new sample type PERF_SAMPLE_LBR_TOS.
Enable LBR_TOS by default in LBR call stack mode.
If kernel doesn't support the sample type, switching it off.
Reviewed-by: Andi Kleen
Signed-off-by: Kan Liang
---
tools/include/uapi/linux/perf_event.h | 4 +++-
tools/perf/uti
On Mon, Oct 7, 2019 at 12:00 PM Andreas Klinger wrote:
>
> Hi Rob,
>
> i don't get this error. Is there anything i'm doing wrong here?
>
> ak@arbad:/project/opt-sw/linux-robh$ make O=../build-wega-robh/
> dt_binding_check
> make[1]: Verzeichnis „/project/opt-sw/build-wega-robh“ wird betreten
>
On 30.09.19 17:38, Halil Pasic wrote:
> Commit 37db8985b211 ("s390/cio: add basic protected virtualization
> support") breaks virtio-ccw devices with VIRTIO_F_IOMMU_PLATFORM for non
> Protected Virtualization (PV) guests. The problem is that the dma_mask
> of the ccw device, which is used by vir
Hi Moritz,
On 9/27/19 1:23 PM, Moritz Fischer wrote:
Thor,
On Fri, Sep 27, 2019 at 09:32:11AM -0500, Thor Thayer wrote:
Hi Kedar & Moritz,
On 9/27/19 12:13 AM, Appana Durga Kedareswara Rao wrote:
Hi Alan,
Did you get a chance to send your framework changes to upstream?
No they weren't upst
On Mon, 2019-10-07 at 17:27 +0200, Vincent Guittot wrote:
> On Mon, 7 Oct 2019 at 17:14, Rik van Riel wrote:
> > On Thu, 2019-09-19 at 09:33 +0200, Vincent Guittot wrote:
> > > runnable load has been introduced to take into account the case
> > > where
> > > blocked load biases the wake up path wh
Since we link purgatory with -r aka we enable "incremental linking"
no checks for unresolved symbols are done while linking the purgatory.
This commit adds an extra check for unresolved symbols by calling ld
without -r before running objcopy to generate purgatory.ro.
This will help us catch missi
Hi s390 maintainers,
This patch mirrors a similar patch for x86, but it has been untested
because I do not have a mainframe to compile on :)
In 5.4-rc1 the 2 different sha256 implementations for the purgatory resp.
for crypto/sha256_generic.c have been consolidated into 1 single shared
implementa
On Sat, Oct 5, 2019 at 9:46 AM Joe Perches wrote:
>
> fallthrough may become a pseudo reserved keyword so this only use of
> fallthrough is better renamed to allow it.
>
> Signed-off-by: Joe Perches
> ---
> net/sctp/sm_make_chunk.c | 12 ++--
> 1 file changed, 6 insertions(+), 6 deletion
On Mon, Oct 07, 2019 at 08:55:55PM +0300, Jarkko Sakkinen wrote:
> But checkpatch.pl will complain about it...
You should not take checkpatch.pl messages to the letter but always
sanity-check them with common sense. In this particular example,
readability is much more important than some tool meas
YueHaibing writes:
> Use devm_platform_ioremap_resource() to simplify the code a bit.
> This is detected by coccinelle.
>
> Signed-off-by: YueHaibing
Reviewed-by: Kevin Hilman
> ---
> drivers/rtc/rtc-meson.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/
On Mon, Oct 7, 2019 at 8:40 AM David Laight wrote:
>
> You don't really want an extra access_ok() for every 'word' of a copy.
Yes you do.
> Some copies have to be done a word at a time.
Completely immaterial. If you can't see the access_ok() close to the
__get/put_user(), you have a bug.
Plus
On Mon, Oct 07, 2019 at 05:20:30PM +0100, Steven Price wrote:
> On 07/10/2019 17:10, Jason Gunthorpe wrote:
> > On Mon, Oct 07, 2019 at 04:38:14PM +0100, Steven Price wrote:
> >> diff --git a/mm/hmm.c b/mm/hmm.c
> >> index 902f5fa6bf93..34fe904dd417 100644
> >> +++ b/mm/hmm.c
> >> @@ -376,7 +376,7
The patch
ASoC: tas2770: Fix snd_soc_update_bits error handling
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.5
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hou
The patch
ASoc: tas2770: Remove unused defines and variables
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.5
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours)
On Mon, Oct 7, 2019 at 10:34 AM Al Viro wrote:
>
> Tangentially related: copy_regster_to_user() and copy_regset_from_user().
Not a worry. It's not performance-critical code, and if it ever is, it
needs to be rewritten anyway.
> The former variant tends to lead to few calls
> of __copy_{to,from}
The patch
ASoC: tas2770: Remove unneeded read of the TDM_CFG3 register
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.5
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next
On Sat, Oct 5, 2019 at 10:17 AM Miguel Ojeda
wrote:
>
> Hi Joe,
>
> On Sat, Oct 5, 2019 at 6:46 PM Joe Perches wrote:
> >
> > Reserve the pseudo keyword 'fallthrough' for the ability to convert the
Have we precedent already for "pseudo keywords?" I kind of like the
double underscore prefix we u
On Fri, 2019-10-04 at 18:33 -0700, Andy Lutomirski wrote:
> On Fri, Oct 4, 2019 at 1:10 PM Edgecombe, Rick P
> wrote:
> >
> > On Fri, 2019-10-04 at 07:56 -0700, Andy Lutomirski wrote:
> > > On Thu, Oct 3, 2019 at 2:38 PM Rick Edgecombe
> > > wrote:
> > > >
> > > > This patchset enables the abil
On 10/6/19 3:29 AM, YueHaibing wrote:
> Use devm_platform_ioremap_resource() to simplify the code a bit.
> This is detected by coccinelle.
>
> Signed-off-by: YueHaibing
Acked-by: Florian Fainelli
--
Florian
On Mon, Oct 07, 2019 at 11:13:27AM -0700, Linus Torvalds wrote:
> On Mon, Oct 7, 2019 at 10:34 AM Al Viro wrote:
> >
> > Tangentially related: copy_regster_to_user() and copy_regset_from_user().
>
> Not a worry. It's not performance-critical code, and if it ever is, it
> needs to be rewritten any
Hi Jones,
Thanks for review, we will fix some comment which your suggestion in next patch
Lee Jones 於 2019年10月4日 週五 下午9:33寫道:
>
> Wolfram,
>
> Would you be kind enough to grep for your name below?
>
> On Tue, 24 Sep 2019, Gene Chen wrote:
>
> > From: Gene Chen
> >
> > Add mfd driver for mt6360
* kan.li...@linux.intel.com wrote:
> Performance impact:
> The processing time may increase with the LBR stitching approach
> enabled. The impact depends on the number of samples with stitched LBRs.
>
> For sqlite's tcltest,
> perf record --call-graph lbr -- make tcltest
> perf report --stitch
On Sun, Oct 6, 2019 at 8:11 PM Linus Torvalds
wrote:
>
> >
> > The last two should just do user_access_begin()/user_access_end()
> > instead of access_ok(). __copy_to_user_inatomic() has very few callers as
> > well:
>
> Yeah, good points.
Looking at it some more this morning, I think it's actu
On Mon, Oct 07, 2019 at 01:50:11PM -0400, Tyler Ramer wrote:
> Shutdown the controller when nvme_remove_dead_controller is
> reached.
>
> If nvme_remove_dead_controller() is called, the controller won't
> be comming back online, so we should shut it down rather than just
> disabling.
>
> Remove n
* tip-bot2 for Ralf Ramsauer wrote:
> The following commit has been merged into the x86/platform branch of tip:
>
> Commit-ID: dac59f1eb78123c3f0e497eb9870ac550c59debb
> Gitweb:
> https://git.kernel.org/tip/dac59f1eb78123c3f0e497eb9870ac550c59debb
> Author:Ralf Ramsauer
>
Add a new function, hub_port_power_cycle() to power cycle port's power.
It'll be used by a following patch.
In addition to that, check the return value of usb_hub_set_port_power(),
so we don't need to wait if the set power operation fails.
Furthermore, remove parameter *hdev from usb_hub_set_port
On Dell TB16, Realtek USB ethernet (r8152) connects to an SMSC hub which
then connects to ASMedia xHCI's root hub:
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/7p, 5000M
|__ Port 2: Dev 3, If 0, Class=Vendor Spec
On Mon, 2019-10-07 at 11:14 -0700, Nick Desaulniers wrote:
> > On Sat, Oct 5, 2019 at 6:46 PM Joe Perches wrote:
> > > Reserve the pseudo keyword 'fallthrough' for the ability to convert the
>
> Have we precedent already for "pseudo keywords?"
Many. see bool vs _Bool, u32 vs uint32_t, etc.
> I
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
> the fixed-regulator will disable this regulator but disable/enable this
> regulator is only valid during suspend/resume. I don't say that my fix
> is correct but
Quoting MarkLee :
Add missing configuration for mt7629 gmii mode support
Fixes: 7e538372694b ("net: ethernet: mediatek: Re-add support SGMII")
Signed-off-by: MarkLee
--
v1->v2:
* no change
---
drivers/net/ethernet/mediatek/mtk_eth_soc.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/driv
Quoting MarkLee :
* Removes mediatek,physpeed property from dtsi that is useless in PHYLINK
* Use the fixed-link property speed = <2500> to set the phy in 2.5Gbit.
* Set gmac1 to gmii mode that connect to a internal gphy
Signed-off-by: MarkLee
--
v1->v2:
* SGMII port only support BASE-X at 2.5
When device stop was moved out of reset, test device wasn't updated to
stop before reset, this resulted in a use after free. Fix by invoking
stop appropriately.
Fixes: b211616d7125 ("vhost: move -net specific code out")
Signed-off-by: Michael S. Tsirkin
---
drivers/vhost/test.c | 2 ++
1 file c
Use seq_puts and simple string output and not seq_printf with formats
and individual strings to reduce overall object size.
$ size drivers/misc/sgi-gru/gruprocfs.o* (x86-64 defconfig with gru)
textdata bss dec hex filename
7006 8 070141b66 drivers/misc/sgi
On 2019-10-07 18:42, Jason Baron wrote:
On 10/7/19 6:54 AM, Roman Penyaev wrote:
On 2019-10-03 18:13, Jason Baron wrote:
On 9/30/19 7:55 AM, Roman Penyaev wrote:
On 2019-09-28 04:29, Andrew Morton wrote:
On Wed, 25 Sep 2019 09:56:03 +0800 hev wrote:
From: Heiher
Take the case where we ha
On Mon, Oct 07, 2019 at 01:58:57PM -0400, Arvind Sankar wrote:
> On Mon, Oct 07, 2019 at 10:56:30AM -0700, Christoph Hellwig wrote:
> > On Mon, Oct 07, 2019 at 07:55:28PM +0200, Christoph Hellwig wrote:
> > > On Mon, Oct 07, 2019 at 01:54:32PM -0400, Arvind Sankar wrote:
> > > > It doesn't boot wit
On 2019-10-07 19:45, Ezequiel Garcia wrote:
> From: Francois Buergisser
>
> The setting of the motion vectors usage and the setting of motion
> vectors address are currently done under different conditions.
>
> When decoding pre-recorded videos, this results of leaving the motion
> vectors address
On Mon, Oct 7, 2019 at 11:28 AM Linus Torvalds
wrote:
>
> On Sun, Oct 6, 2019 at 8:11 PM Linus Torvalds
> wrote:
> >
> > >
> > > The last two should just do user_access_begin()/user_access_end()
> > > instead of access_ok(). __copy_to_user_inatomic() has very few callers
> > > as well:
> >
> >
On Mon, Oct 7, 2019 at 12:56 PM John Stultz wrote:
>
> Add necessary compatible flag for HiSi's DWC3 so
> dwc3-of-simple will probe.
>
> Cc: Greg Kroah-Hartman
> Cc: Felipe Balbi
> Cc: Andy Shevchenko
> Cc: Rob Herring
> Cc: Mark Rutland
> Cc: Yu Chen
> Cc: Matthias Brugger
> Cc: Chunfeng Y
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 as a new managed wrapper to ioremap_uc
and with it overwrite the MTRR set
On 10/7/19 2:30 PM, Roman Penyaev wrote:
> On 2019-10-07 18:42, Jason Baron wrote:
>> On 10/7/19 6:54 AM, Roman Penyaev wrote:
>>> On 2019-10-03 18:13, Jason Baron wrote:
On 9/30/19 7:55 AM, Roman Penyaev wrote:
> On 2019-09-28 04:29, Andrew Morton wrote:
>> On Wed, 25 Sep 2019 09:5
On Mon, Oct 07, 2019 at 02:32:07PM -0400, Arvind Sankar wrote:
> On Mon, Oct 07, 2019 at 01:58:57PM -0400, Arvind Sankar wrote:
> > On Mon, Oct 07, 2019 at 10:56:30AM -0700, Christoph Hellwig wrote:
> > > On Mon, Oct 07, 2019 at 07:55:28PM +0200, Christoph Hellwig wrote:
> > > > On Mon, Oct 07, 201
Hi Takashi,
> On Sep 25, 2019, at 19:32, Kai-Heng Feng wrote:
>
> Nvidia proprietary driver doesn't support runtime power management, so
> when a user only wants to use the integrated GPU, it's a common practice
> to let dGPU not to bind any driver, and let its upstream port to be
> runtime susp
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 which already handles many of
> the requirements discussed here.
Versal is xilinx's next generation soc. This patch adds
driver support required to be compatible with versal device.
Signed-off-by: Jolly Shah
---
drivers/firmware/xilinx/zynqmp.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/firmware/xilinx/zynqmp.c b/drive
Versal is xilinx's next generation soc. This patch adds
driver support required to be compatible with versal device
v2:
No changes. Resending to include DT maintaners
Jolly Shah (2):
dt-bindings: firmware: Add bindings for Versal firmware
drivers: firmware: xilinx: Add support for versal so
ZynqMP firmware driver can be used for versal also.
Add versal compatible string to zynqmp firmware driver
doc.
Signed-off-by: Jolly Shah
---
.../bindings/firmware/xilinx/xlnx,zynqmp-firmware.txt| 16 +++-
1 file changed, 15 insertions(+), 1 deletion(-)
diff --git
a/Documentati
Hi Michal and Greg,
> -Original Message-
> From: Michal Simek
> Sent: Sunday, October 06, 2019 11:14 PM
> To: Greg KH ; Jolly Shah
> Cc: ard.biesheu...@linaro.org; mi...@kernel.org; m...@codeblueprint.co.uk;
> sudeep.ho...@arm.com; hkallwe...@gmail.com; keesc...@chromium.org;
> dmitry.to
Hello,
syzbot found the following crash on:
HEAD commit:056ddc38 Merge branch 'stmmac-next'
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=144ea69960
kernel config: https://syzkaller.appspot.com/x/.config?x=d9be300620399522
dashboard link: https://syz
Hello,
syzbot found the following crash on:
HEAD commit:056ddc38 Merge branch 'stmmac-next'
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1590218f60
kernel config: https://syzkaller.appspot.com/x/.config?x=d9be300620399522
dashboard link: https://syz
Hello,
syzbot found the following crash on:
HEAD commit:3b47fd5c Merge tag 'nfs-for-5.3-4' of git://git.linux-nfs...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12e278c160
kernel config: https://syzkaller.appspot.com/x/.config?x=b89bb446a3faaba4
da
Hello,
syzbot found the following crash on:
HEAD commit:056ddc38 Merge branch 'stmmac-next'
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=164f0c5760
kernel config: https://syzkaller.appspot.com/x/.config?x=d9be300620399522
dashboard link: https://syz
Hello,
syzbot found the following crash on:
HEAD commit:056ddc38 Merge branch 'stmmac-next'
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=168bdd4760
kernel config: https://syzkaller.appspot.com/x/.config?x=d9be300620399522
dashboard link: https://syz
Hello,
syzbot found the following crash on:
HEAD commit:056ddc38 Merge branch 'stmmac-next'
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=176f00dd60
kernel config: https://syzkaller.appspot.com/x/.config?x=d9be300620399522
dashboard link: https://syz
update powerpc ima buffer pass implementationt to call into
of_ima* for a cross architecture support.
Signed-off-by: Prakhar Srivastava
---
arch/powerpc/include/asm/ima.h | 6 --
arch/powerpc/kernel/Makefile| 8 +-
arch/powerpc/kernel/ima_kexec.c | 170 +++-
As per "AMD64 Architecture Programmer's Manual Volume 3: General-Purpose
and System Instructions", MWAITX EAX[7:4]+1 specifies the optional hint
of the optimized C-state. For C0 state, EAX[7:4] should be set to 0xf.
Currently, a value of 0xf is set for EAX[3:0] instead of EAX[7:4]. Fix
this by cha
Hi All:
drivers/target/iscsi/cxgbit/cxgbit_ddp.c:
Inside function cxgbit_ddp_sgl_check(), sg_next() could return NULL,
however, the return value of sg_next() is not checked and get
dereferenced. This could potentially be unsafe.
--
Kind Regards,
Yizhuo Zhai
Computer Science, Graduate Student
On 10/7/19 12:55 AM, Michal Hocko wrote:
> From: David Rientjes
>
> b39d0ee2632d ("mm, page_alloc: avoid expensive reclaim when compaction
> may not succeed") has chnaged the allocator to bail out from the
> allocator early to prevent from a potentially excessive memory
> reclaim. __GFP_RETRY_MAY
From: Antonio Borneo
Date: Mon, 7 Oct 2019 17:43:02 +0200
> Fix typo s/mechansim/mechanism/
>
> Signed-off-by: Antonio Borneo
Applied, thank you.
On Mon, Oct 7, 2019 at 11:38 AM Rob Herring wrote:
>
> On Mon, Oct 7, 2019 at 12:56 PM John Stultz wrote:
> >
> > Add necessary compatible flag for HiSi's DWC3 so
> > dwc3-of-simple will probe.
> >
> > Cc: Greg Kroah-Hartman
> > Cc: Felipe Balbi
> > Cc: Andy Shevchenko
> > Cc: Rob Herring
> >
[+Linus]
On Mon, Oct 07, 2019 at 07:30:07AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:43b815c6 Merge tag 'armsoc-fixes' of git://git.kernel.org/..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=10721dfb6
On Mon, Oct 07, 2019 at 07:31:07AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:43b815c6 Merge tag 'armsoc-fixes' of git://git.kernel.org/..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=12165d0b60
> kernel
On Mon, Oct 7, 2019 at 11:36 AM Tony Luck wrote:
>
> Late to this party ,,, but my ia64 console today is full of:
Hmm? I thought ia64 did unaligneds ok.
But regardless, this is my current (as yet untested) patch. This is
not the big user access cleanup that I hope Al will do, this is just a
"ok
Dne ponedeljek, 07. oktober 2019 ob 12:44:24 CEST je Hans Verkuil napisal(a):
> Hi Jernej,
>
> On 9/29/19 10:00 PM, Jernej Skrabec wrote:
> > This series adds support for decoding multi-slice H264 frames along with
> > support for V4L2_DEC_CMD_FLUSH and V4L2_BUF_FLAG_M2M_HOLD_CAPTURE_BUF.
> >
> >
On 2019-10-07 20:43, Jason Baron wrote:
On 10/7/19 2:30 PM, Roman Penyaev wrote:
On 2019-10-07 18:42, Jason Baron wrote:
On 10/7/19 6:54 AM, Roman Penyaev wrote:
On 2019-10-03 18:13, Jason Baron wrote:
On 9/30/19 7:55 AM, Roman Penyaev wrote:
On 2019-09-28 04:29, Andrew Morton wrote:
On Wed
Mon, Oct 07, 2019 at 08:59:11PM CEST,
syzbot+896295c817162503d...@syzkaller.appspotmail.com wrote:
>Hello,
>
>syzbot found the following crash on:
>
>HEAD commit:056ddc38 Merge branch 'stmmac-next'
>git tree: net-next
>console output: https://syzkaller.appspot.com/x/log.txt?x=1590218f600
From: James Bottomley
Subject: [PATCH] tpm: use GFP kernel for tpm_buf allocations
The current code uses GFP_HIGHMEM, which is wrong because GFP_HIGHMEM
(on 32 bit systems) is memory ordinarily inaccessible to the kernel
and should only be used for allocations affecting userspace. In order
to ma
Hi All:
drivers/net/wireless/intel/iwlwifi/mvm/power.c:
Inside function iwl_mvm_power_ps_disabled_iterator(),
iwl_mvm_vif_from_mac80211()
could return NULL,however, the return value of
iwl_mvm_vif_from_mac80211() is not
checked and get
used. This could potentially be unsafe.
--
Kind Regards,
Y
On Mon, Oct 7, 2019 at 12:07 PM Eric Biggers wrote:
>
> Seems this indicates a corrupt filesystem rather than a kernel bug, so using
> WARN_ON is not appropriate. It should either use pr_warn_once(), or be
> silent.
I was going to silence it for the actual 5.4 release, but I wanted to
see if an
On Monday 07 October 2019 15:10:05 Gene Heskett wrote:
> On Monday 16 September 2019 17:39:21 Steven Rostedt wrote:
> > Dear RT Folks,
> >
> > I'm pleased to announce the 4.19.72-rt25 stable release.
> >
> >
> >
> > As you probably have noticed, it has been a long time since I
> > relea
On Mon, Oct 07, 2019 at 09:11:02PM +0200, Jiri Pirko wrote:
> Mon, Oct 07, 2019 at 08:59:11PM CEST,
> syzbot+896295c817162503d...@syzkaller.appspotmail.com wrote:
> >Hello,
> >
> >syzbot found the following crash on:
> >
> >HEAD commit:056ddc38 Merge branch 'stmmac-next'
> >git tree: net
On Mon, 2019-10-07 at 13:03 +0300, Andy Shevchenko wrote:
> On Fri, Oct 04, 2019 at 10:15:21AM -0700, Srinivas Pandruvada wrote:
> > On Thu, 2019-10-03 at 08:11 -0400, Prarit Bhargava wrote:
> > > + /* only three CascadeLake-N models are supported */
> > > + if (is_clx_n_platform()) {
> > > +
Hi All:
drivers/net/wireless/intel/iwlwifi/mvm/scan.c:
Inside function iwl_mvm_power_ps_disabled_iterator(),
iwl_mvm_vif_from_mac80211()
could return NULL,however, the return value of
iwl_mvm_vif_from_mac80211() is not checked and get
used. This could potentially be unsafe.
--
Kind Regards,
Yi
1 - 100 of 1238 matches
Mail list logo