Define and export OBJSIZE variable for "size" tool from binutils to be
used in architecture specific Makefiles (naming the variable just "SIZE"
would be too risky). In particular this tool is useful to perform checks
that early boot code is not using bss section (which might have not been
zeroed ye
On Tue, Aug 06, 2019 at 04:11:23PM +0800, Wei Yang wrote:
> When addr is out of the range of the whole rb_tree, pprev will points to
> the biggest node. find_vma_prev gets is by going through the right most
> node of the tree.
>
> Since only the last node is the one it is looking for, it is not
>
Linus,
please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/hid/hid.git for-linus
to receive HID subsystem fixes:
=
- functional regression fix for some of the Logitech unifying devices,
from Hans de Goede
- race condition fix in hid-sony for bug severely affecting Valve/Andr
On Tue, Aug 06, 2019 at 10:04:15AM +0200, Michal Hocko wrote:
> On Tue 06-08-19 15:05:47, kernel test robot wrote:
> > Greeting,
> >
> > FYI, we noticed a -4.1% regression of will-it-scale.per_process_ops due to
> > commit:
>
> I have to confess I cannot make much sense from numbers because they
On 8/6/19 12:39 AM, Gustavo A. R. Silva wrote:
Fix the following warning (Building: ci20_defconfig mips):
drivers/watchdog/jz4740_wdt.c: In function ‘jz4740_wdt_probe’:
drivers/watchdog/jz4740_wdt.c:165:6: warning: unused variable ‘ret’
[-Wunused-variable]
int ret;
^~~
Fixes: 9ee644c9
On 06/08/2019 11:01, Marc Zyngier wrote:
It looks like the HIP06/07 SoCs have extra bits in their GICD_TYPER
registers, which confuse the GICv3.1 code (these systems appear to
expose ESPIs while they actually don't).
Detect these systems as early as possible and wipe the fields that
should be RE
On 2/08/19 8:39 PM, Shirley Her (SC) wrote:
> Fix data read/write error in HS200 mode due to chip DLL lock phase shift
>
> Signed-off-by:Shirley Her
> ---
> change in V4:
> 1. add a bug fix in V3
>
> change in V3:
> 1. add more explanation in dll_recovery and execute_tuning function
> 2. move
On Tue 06-08-19 20:00:24, Minchan Kim wrote:
> On Tue, Aug 06, 2019 at 10:04:15AM +0200, Michal Hocko wrote:
> > On Tue 06-08-19 15:05:47, kernel test robot wrote:
> > > Greeting,
> > >
> > > FYI, we noticed a -4.1% regression of will-it-scale.per_process_ops due
> > > to commit:
> >
> > I have
Hi,
On 2019-08-06 15:26, Claire Chang wrote:
commit 32646db8cc28 ("Bluetooth: btqca: inject command complete event
during fw download") added qca_inject_cmd_complete_event() for certain
qualcomm chips. However, qca_download_firmware() will return without
calling release_firmware() in this case.
On Mon, Aug 05, 2019 at 09:56:45AM -0600, William Kucharski wrote:
> >> I don't really care if the start of the VMA is suitable, just whether I
> >> can map
> >> the current faulting page with a THP. As far as I know, there's nothing
> >> wrong
> >> with mapping all the pages before the VMA hits
Hi Yabin
On 06/08/2019 00:37, Yabin Cui wrote:
TMC etr always copies all available data to perf aux buffer, which
may exceed the available space in perf aux buffer. It isn't suitable
for not-snapshot mode, because:
1) It may overwrite previously written data.
2) It may make the perf_event_mmap_p
On Tue 06-08-19 20:07:37, Minchan Kim wrote:
> On Tue, Aug 06, 2019 at 12:47:55PM +0200, Michal Hocko wrote:
> > On Tue 06-08-19 06:36:27, Joel Fernandes wrote:
> > > On Tue, Aug 06, 2019 at 10:42:03AM +0200, Michal Hocko wrote:
> > > > On Mon 05-08-19 13:04:49, Joel Fernandes (Google) wrote:
> > >
On Tue, Jul 30, 2019 at 10:59 AM Nicolin Chen wrote:
>
> On Mon, Jul 29, 2019 at 09:20:01PM +0100, Mark Brown wrote:
> > On Mon, Jul 29, 2019 at 10:57:43PM +0300, Daniel Baluta wrote:
> > > On Mon, Jul 29, 2019 at 10:42 PM Nicolin Chen
> > > wrote:
> > > > On Sun, Jul 28, 2019 at 10:24:23PM +030
Hi Vladimir,
On 06/08/2019 11:15, Vladimir Murzin wrote:
> Hi Marc,
>
> On 8/6/19 11:01 AM, Marc Zyngier wrote:
>> As is it usual for the GIC, it isn't disallowed to put together a system
>> that is majorly inconsistent, with a distributor supporting the
>> extended ranges while some of the CPUs
Commit-ID: f4904815f97a934258445a8f763f6b6c48f007e7
Gitweb: https://git.kernel.org/tip/f4904815f97a934258445a8f763f6b6c48f007e7
Author: Dietmar Eggemann
AuthorDate: Fri, 2 Aug 2019 15:59:43 +0100
Committer: Peter Zijlstra
CommitDate: Tue, 6 Aug 2019 12:49:18 +0200
sched/deadline: Fix d
On Tue, Aug 06, 2019 at 12:51:49PM +0200, Michal Hocko wrote:
> On Tue 06-08-19 06:45:54, Joel Fernandes wrote:
> > On Tue, Aug 06, 2019 at 10:43:57AM +0200, Michal Hocko wrote:
> > > On Mon 05-08-19 13:04:50, Joel Fernandes (Google) wrote:
> > > > During idle tracking, we see that sometimes faulte
Commit-ID: 04e048cf09d7b5fc995817cdc5ae1acd4482429c
Gitweb: https://git.kernel.org/tip/04e048cf09d7b5fc995817cdc5ae1acd4482429c
Author: Suren Baghdasaryan
AuthorDate: Mon, 29 Jul 2019 18:33:10 -0700
Committer: Peter Zijlstra
CommitDate: Tue, 6 Aug 2019 12:49:18 +0200
sched/psi: Do not
On Mon, Aug 5, 2019 at 10:19 PM Guenter Roeck wrote:
> On Mon, Aug 05, 2019 at 09:57:59PM +0200, Arnd Bergmann wrote:
> > On Mon, Aug 5, 2019 at 8:52 PM Guenter Roeck wrote:
> > > On Mon, Aug 05, 2019 at 08:35:40PM +0200, Arnd Bergmann wrote:
> > >
> > > No. I see the failure in next-20190729..ne
The generic vdso support adds the same #if hack in two places,
asm/vdso/vdso.h and config-n32-o32-env.c, but only the second
is actually used. The result lacks the BUILD_VDSO32_64 macro,
and that triggers a build error:
./include/linux/page-flags-layout.h:95:2: error: #error "Not enough bits in
p
Hi Dave,
here's a pull request to net tree for v5.3, more information below.
Please let me know if there are any problems.
Kalle
The following changes since commit 5f9e832c137075045d15cd6899ab0505cfb2ca4b:
Linus 5.3-rc1 (2019-07-21 14:05:38 -0700)
are available in the git repository at:
g
This change prints the hexadecimal EC value in mem_abort_decode(),
which makes it easier to lookup the corresponding EC in
the ARM Architecture Reference Manual.
The commit 1f9b8936f36f ("arm64: Decode information from ESR upon mem
faults") prints useful information when memory abort occurs. It wo
On 2/08/19 8:40 PM, Shirley Her (SC) wrote:
> Fix data read/write error in HS200 mode due to chip DLL lock phase shift
>
> Signed-off-by:Shirley Her
> ---
> change in V4:
> 1. add a bug fix for V3
>
> change in V3:
> 1. add more explanation in dll_recovery and execute_tuning function
> 2. move
On Mon, Aug 05, 2019 at 09:27:16AM -0700, Alexander Duyck wrote:
> On Mon, 2019-08-05 at 12:00 -0400, Nitesh Narayan Lal wrote:
> > On 8/1/19 6:38 PM, Alexander Duyck wrote:
> > > From: Alexander Duyck
> > >
> > > Add support for the page reporting feature provided by virtio-balloon.
> > > Report
On Tue, Aug 06, 2019 at 11:57:26AM +0200, Paul Menzel wrote:
> Dear Mika,
>
>
> Thank you for your quick reply.
>
>
> On 06.08.19 11:36, Mika Westerberg wrote:
> > +Nicholas and Matthias
> >
> > On Tue, Aug 06, 2019 at 11:20:37AM +0200, Paul Menzel wrote:
>
> >> Commit c2bf1fc2 (PCI: Add miss
Chris Packham writes:
> On Mon, 2019-08-05 at 14:06 +1200, Chris Packham wrote:
>> Hi All,
>>
>> I have a custom board that uses the Freescale/NXP T2080 SoC.
>>
>> The board boots fine using v4.19.60 but when I use v5.1.21 it locks
>> up
>> waiting for the other CPUs to come online (earlyprintk
On 8/6/2019 4:34 PM, Jiri Olsa wrote:
On Thu, Jul 25, 2019 at 06:14:32AM +0800, Jin Yao wrote:
SNIP
static int cycles_printf(struct hist_entry *he, struct hist_entry *pair,
-struct perf_hpp *hpp, int width)
+struct perf_hpp *hpp, int width _
> v2->v3: change subject of patch.
Will it be nicer to use the word “compilation” in your patch subject?
> v3->v4: change the alignment of two functions.
I would refer to an adjusted indentation.
How do you think about to omit “arrows” in these version identifications?
Regards,
Markus
On 8/6/2019 4:34 PM, Jiri Olsa wrote:
On Thu, Jul 25, 2019 at 06:14:32AM +0800, Jin Yao wrote:
SNIP
+}
+
double avg_stats(struct stats *stats)
{
return stats->mean;
diff --git a/tools/perf/util/stat.h b/tools/perf/util/stat.h
index 95b4de7a9d51..3448d319a220 100644
--- a/tools/p
Hi Belloni,
On Mon, 2019-08-05 at 09:23 +0200, Alexandre Belloni wrote:
> Hi,
>
> The subject should be:
>
> "rtc: mt6397: Add support for the MediaTek MT6358 RTC"
Will be changed at next patch.
> > +struct mtk_rtc_compatible {
>
> I would name that struct mtk_rtc_data
>
> > + u32
From: Bartosz Golaszewski
If the driver doesn't support open-drain/source config options, we
emulate this behavior when setting the direction by calling
gpiod_direction_input() if the default value is 0 (open-source) or
1 (open-drain), thus not actively driving the line in those cases.
This howe
On 8/6/2019 4:34 PM, Jiri Olsa wrote:
On Thu, Jul 25, 2019 at 06:14:32AM +0800, Jin Yao wrote:
This patch prints the stddev and hist for the cycles diff of
program block. It can help us to understand if the cycles diff
is noisy or not.
This patch is inspired by Andi Kleen's patch
https://lwn
On Mon, 2019-08-05 at 16:11 +0200, Andrew Lunn wrote:
> [External]
>
> > + adi,rx-internal-delay:
> > +$ref: /schemas/types.yaml#/definitions/uint32
> > +description: |
> > + RGMII RX Clock Delay used only when PHY operates in RGMII mode
> > (phy-mode
> > + is "rgmii-id", "rgmi
On Sun, Aug 04, 2019 at 04:07:17AM -0400, Michael S. Tsirkin wrote:
> > > > Also, why can't this just permanently GUP the pages? In fact, where
> > > > does it put_page them anyhow? Worrying that 7f466 adds a get_user page
> > > > but does not add a put_page??
> >
> > You didn't answer this.. Why
On Mon, Aug 05, 2019 at 10:33:29PM -0300, Jose Carlos Cazarin Filho wrote:
> Fix checkpath warning:
> WARNING: Unnecessary typecast of c90 int constant
>
> Signed-off-by: Jose Carlos Cazarin Filho
> ---
> Hello all!
> This is my first commit to the Linux Kernel, I'm doing this to learn and be
Fixed WARNING: else is not generally useful after a break or return
---
drivers/staging/rtl8188eu/core/rtw_security.c | 41 +--
1 file changed, 20 insertions(+), 21 deletions(-)
diff --git a/drivers/staging/rtl8188eu/core/rtw_security.c
b/drivers/staging/rtl8188eu/core/rtw_securi
On 2/08/19 1:53 PM, Chevron Li (WH) wrote:
> Hi, Adrian,
>
> Firstly, really appreciate for your valuable suggestions.
>
> For your question that " Tuning will be executed whenever the system resumes,
> which is not an error. Can you explain when error recovery is needed,
> and how this patch wo
On Tue, Aug 6, 2019 at 9:54 AM Jinpu Wang wrote:
>
> On Tue, Aug 6, 2019 at 1:46 AM NeilBrown wrote:
> >
> > On Mon, Aug 05 2019, Jinpu Wang wrote:
> >
> > > Hi Neil,
> > >
> > > For the md higher write IO latency problem, I bisected it to these
> > > commits:
> > >
> > > 4ad23a97 MD: use per-cp
Hello Philipp,
On Tue, 6 Aug 2019 at 10:12, Philipp Wendler wrote:
>
> Hello Michael, hello Aleksa,
>
> Am 05.08.19 um 14:29 schrieb Michael Kerrisk (man-pages):
>
> > On 8/5/19 12:36 PM, Aleksa Sarai wrote:
> >> On 2019-08-01, Michael Kerrisk (man-pages) wrote:
> >>> I'd like to add some docume
On Tue, Aug 06, 2019 at 05:24:38PM +0530, Merwin Trever Ferrao wrote:
> Fixed WARNING: else is not generally useful after a break or return
> ---
Much better, but you forgot the the Signed-off-by so we can't apply it.
Also it's nice to be more specific with the subject.
[PATCH] Staging: rtl8188eu
On Mon, Aug 05, 2019 at 12:20:45PM +0800, Jason Wang wrote:
>
> On 2019/8/2 下午8:46, Jason Gunthorpe wrote:
> > On Fri, Aug 02, 2019 at 05:40:07PM +0800, Jason Wang wrote:
> > > > This must be a proper barrier, like a spinlock, mutex, or
> > > > synchronize_rcu.
> > >
> > > I start with synchroniz
On Mon, Aug 05, 2019 at 11:50:03PM -0400, Qian Cai wrote:
>
>
> > On Aug 5, 2019, at 10:01 AM, Will Deacon wrote:
> >
> > On Mon, Aug 05, 2019 at 07:47:37AM -0400, Qian Cai wrote:
> >>
> >>
> >>> On Aug 5, 2019, at 5:52 AM, Will Deacon wrote:
> >>>
> >>> On Fri, Aug 02, 2019 at 11:32:24AM -
On Tue, Aug 06, 2019 at 03:44:34PM +0530, Rayagonda Kokatanur wrote:
> Switch back to BSPI mode after MSPI operations (write and erase)
> are completed. This change will keep qpsi in BSPI mode by default.
Why?
signature.asc
Description: PGP signature
On Tue, Aug 6, 2019 at 10:38 AM Omer Shpigelman wrote:
>
> This patch improves the security in the Debug IOCTL.
> It adds checks that:
> - The register index value is in the allowed range for all opcodes.
> - The event types number is in the allowed range in SPMU enable.
> - The events number is i
> >
> > I also think a way to make fairness per cookie per core, is this what you
> > want to propose?
>
> Yes, that's what I meant.
I think that would hurt some kind of workloads badly, especially if
one tenant is
having way more tasks than the other. Tenant with more task on the same core
might
Chuhong Yuan wrote:
> Instead of using to_pci_dev + pci_get_drvdata,
> use dev_get_drvdata to make code simpler.
>
> Signed-off-by: Chuhong Yuan
Patch applied to wireless-drivers-next.git, thanks.
9236c1250cb7 bcma: Use dev_get_drvdata
--
https://patchwork.kernel.org/patch/11054111/
https:
This code generates checkpatch warning:
WARNING: else is not generally useful after a break or return
Moving the declaration to the top of the function we can pull the
code back one tab and it makes it more readable.
Signed-off-by: Merwin Trever Ferrao
---
drivers/staging/rtl8188eu/core/rtw_se
Pavel Machek writes:
> Surrounding code uses -ERRNO as a result, so don't pass plain -1.
>
> Signed-off-by: Pavel Machek
For some reason patchwork (or my patchwork script) didn't like this
patch:
Failed to apply the patch: ['git', 'am', '-s', '-3'] failed: 128
Patch is empty. Was it split wron
Chuhong Yuan wrote:
> Instead of using to_pci_dev + pci_get_drvdata,
> use dev_get_drvdata to make code simpler.
>
> Signed-off-by: Chuhong Yuan
4 patches applied to wireless-drivers-next.git, thanks.
a40c28700d98 iwlegacy: Use dev_get_drvdata where possible
ffa4d78cbc26 mwifiex: pcie: Use de
YueHaibing wrote:
> Now _rtl_dump_channel_map() does not do any actual
> thing using the channel. So remove it.
>
> Signed-off-by: YueHaibing
> Acked-by: Ping-Ke Shih
Patch applied to wireless-drivers-next.git, thanks.
a4a68f727fb8 rtlwifi: remove unneeded function _rtl_dump_channel_map()
-
On Tue, Aug 06, 2019 at 07:29:48PM +0800, Miles Chen wrote:
> This change prints the hexadecimal EC value in mem_abort_decode(),
> which makes it easier to lookup the corresponding EC in
> the ARM Architecture Reference Manual.
>
> The commit 1f9b8936f36f ("arm64: Decode information from ESR upon
Navid Emamdoost wrote:
> devm_kzalloc may fail and return NULL. So the null check is needed.
>
> Signed-off-by: Navid Emamdoost
> Acked-by: Jakub Kicinski
Patch applied to wireless-drivers-next.git, thanks.
b95c732234fa mt7601u: null check the allocation
--
https://patchwork.kernel.org/pat
YueHaibing wrote:
> Fixes gcc '-Wunused-but-set-variable' warning:
>
> drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c: In function
> brcmf_update_bss_info:
> drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c:2962:5: warning:
> variable dtim_period set but not used [-Wunu
+ rostedt.
Steve, pls have a look at the patch at the beginning of this thread as
it touches the reentrant NMI magic. :)
Thx.
On Tue, Aug 06, 2019 at 10:30:32AM +0200, Peter Zijlstra wrote:
> On Tue, Aug 06, 2019 at 07:08:51AM +0200, Borislav Petkov wrote:
> > On Mon, Aug 05, 2019 at 10:50:30AM
Colin King wrote:
> From: Colin Ian King
>
> Variable err is initialized to a value that is never read and it
> is re-assigned later. The initialization is redundant and can
> be removed.
>
> Addresses-Coverity: ("Unused value")
> Signed-off-by: Colin Ian King
Patch applied to wireless-driv
YueHaibing wrote:
> Fixes gcc '-Wunused-but-set-variable' warning:
>
> drivers/net/wireless/broadcom/brcm80211/brcmsmac/main.c: In function
> 'brcms_c_set_gmode':
> drivers/net/wireless/broadcom/brcm80211/brcmsmac/main.c:5257:7: warning:
> variable 'preamble_restrict' set but not used [-Wunuse
YueHaibing wrote:
> Fixes gcc '-Wunused-but-set-variable' warning:
>
> drivers/net/wireless/realtek/rtw88/pci.c: In function 'rtw_pci_phy_cfg':
> drivers/net/wireless/realtek/rtw88/pci.c:993:6: warning:
> variable 'ip_sel' set but not used [-Wunused-but-set-variable]
>
> Reported-by: Hulk Robo
Masanari Iida wrote:
> This patch add a device ID for PLANEX GW-USMicroN.
> Without this patch, I had to echo the device IDs in order to
> recognize the device.
>
> # lsusb |grep PLANEX
> Bus 002 Device 005: ID 2019:ed14 PLANEX GW-USMicroN
>
> Signed-off-by: Masanari Iida
> Acked-by: Stanislaw
Hi,
On Tue, Aug 6, 2019 at 2:39 AM Michal Simek wrote:
>
> On 06. 08. 19 5:07, Luis Araneda wrote:
> > Add .arm directive to headsmp.S to ensure that the
> > CPU starts in 32-bit ARM mode and the correct code
> > size is copied on smp bring-up
> >
> > Additionally, start secondary CPUs on seconda
"Enrico Weigelt, metux IT consult" wrote:
> From: Enrico Weigelt
>
> Explicitly return constants instead of variable (and rely on
> it to be explicitly initialized), if the value is supposed
> to be fixed anyways. Align it with the rest of the driver,
> which does it the same way.
>
> Signed-o
On Mon, Aug 05, 2019 at 03:02:40PM +0200, Greg Kroah-Hartman wrote:
[ Upstream commit 449fa54d6815be8c2c1f68fa9dbbae9384a7c03e ]
dma_map_sg() may use swiotlb buffer when the kernel command line includes
"swiotlb=force" or the dma_addr is out of dev->dma_mask range. After
DMA complete the memory
Brian Norris wrote:
> This reverts commit 437322ea2a36d112e20aa7282c869bf924b3a836.
>
> This above-mentioned "fix" does not actually do anything to prevent a
> race condition. It simply papers over it so that the issue doesn't
> appear.
>
> If this is a real problem, it should be explained bett
On Tue, Jun 25, 2019 at 10:39:13AM -0400, Waiman Long wrote:
> When the handoff bit is set by a writer, no other tasks other than
> the setting writer itself is allowed to acquire the lock. If the
> to-be-handoff'ed writer goes to sleep, there will be a wakeup latency
> period where the lock is fre
On Wed, Jul 31, 2019 at 2:39 PM YueHaibing wrote:
> when do randbuilding, I got this error:
>
> In file included from drivers/hwmon/pmbus/ucd9000.c:19:0:
> ./include/linux/gpio/driver.h:576:1: error: redefinition of
> gpiochip_add_pin_range
> gpiochip_add_pin_range(struct gpio_chip *chip, const
> +++ b/drivers/md/dm-raid1.c
> @@ -878,12 +878,9 @@ static struct mirror_set *alloc_context(unsigned int
> nr_mirrors,
> struct dm_target *ti,
> struct dm_dirty_log *dl)
> {
> - size_t len;
> struct mirror_set
On 06/08/2019 00:09, Rob Herring wrote:
> On Mon, Aug 5, 2019 at 6:26 AM Neil Armstrong wrote:
>>
>> Now that we have the DT validation in place, let's convert the device tree
>> bindings for the Synopsys DWMAC Glue for Amlogic SoCs over to a YAML schemas.
>>
>> Signed-off-by: Neil Armstrong
>> -
Masoud Sharbiani noticed that commit 29ef680ae7c21110 ("memcg, oom: move
out_of_memory back to the charge path") broke memcg OOM called from
__xfs_filemap_fault() path. It turned out that try_charge() is retrying
forever without making forward progress because mem_cgroup_oom(GFP_NOFS)
cannot invoke
Hi Hui,
On Tue, Aug 6, 2019 at 4:59 AM Hui Song wrote:
> From: Song Hui
>
> Update the NXP GPIO node dt-binding file for QorIQ and
> Layerscape platforms, and add one more example with
> ls1028a GPIO node.
>
> Signed-off-by: Song Hui
(...)
> +Example of gpio-controller node for a ls1028a SoC:
Looks good.
Reviewed-by: Dan Carpenter
regards,
dan carpenter
The Amlogic Meson DWMAC glue bindings needs a second reg cells for the
glue registers, thus update the reg minItems/maxItems to allow more
than a single reg cell.
Signed-off-by: Neil Armstrong
---
Documentation/devicetree/bindings/net/snps,dwmac.yaml | 3 ++-
1 file changed, 2 insertions(+), 1 d
Now that we have the DT validation in place, let's convert the device tree
bindings for the Synopsys DWMAC Glue for Amlogic SoCs over to a YAML schemas.
Signed-off-by: Neil Armstrong
---
.../bindings/net/amlogic,meson-dwmac.yaml | 113 ++
.../devicetree/bindings/net/meson-dwm
Hi Michal,
On Tue, Aug 6, 2019 at 2:42 AM Michal Simek wrote:
> On 06. 08. 19 5:07, Luis Araneda wrote:
> > This fixes a kernel panic (read overflow) on memcpy when
> > FORTIFY_SOURCE is enabled.
> >
> > The computed size of memcpy args are:
> > - p_size (dst): 4294967295 = (size_t) -1
> > - q_si
This patchsets converts the Amlogic Meson DWMAC glue bindings over to
YAML schemas using the already converted dwmac bindings.
The first patch is needed because the Amlogic glue needs a supplementary
reg cell to access the DWMAC glue registers.
Neil Armstrong (2):
dt-bindings: net: snps,dwmac:
On Tue, Aug 6, 2019 at 2:36 PM Oliver Neukum wrote:
>
> Am Donnerstag, den 01.08.2019, 14:47 -0400 schrieb Alan Stern:
> >
> > I think this must be caused by an unbalanced refcount. That is,
> > something must drop one more reference to the device than it takes.
> > That would explain why the inv
Good evening from SINGAPORE,
What are the differences between cointelpro, coamdpro and convidiapro?
Thank you.
-BEGIN EMAIL SIGNATURE-
The Gospel for all Targeted Individuals (TIs):
[The New York Times] Microwave Weapons Are Prime Suspect in Ills of
U.S. Embassy Workers
Link:
https:/
On Tue, Aug 06, 2019 at 02:04:16PM +0800 Hillf Danton wrote:
>
> On Mon, 5 Aug 2019 22:07:05 +0800 Phil Auld wrote:
> >
> > If we're to clear that flag right there, outside of the lock pinning code,
> > then I think we might as well just remove the flag and all associated
> > comments etc, no?
>
On 06/08/2019 13:41, Sasha Levin wrote:
On Mon, Aug 05, 2019 at 03:02:40PM +0200, Greg Kroah-Hartman wrote:
[ Upstream commit 449fa54d6815be8c2c1f68fa9dbbae9384a7c03e ]
dma_map_sg() may use swiotlb buffer when the kernel command line includes
"swiotlb=force" or the dma_addr is out of dev->dma_m
On 2019/8/6 5:18 下午, Andrea Righi wrote:
> bcache_allocator() can call the following:
>
> bch_allocator_thread()
> -> bch_prio_write()
> -> bch_bucket_alloc()
> -> wait on &ca->set->bucket_wait
>
> But the wake up event on bucket_wait is supposed to come from
> bch_allocator_threa
On Mon, 2019-08-05 at 17:37 +0100, Mark Brown wrote:
> On Mon, Aug 05, 2019 at 11:07:58AM +, Philippe Schenker wrote:
> > On Wed, 2019-07-31 at 22:23 +0100, Mark Brown wrote:
>
> Please fix your mail client to word wrap within paragraphs at something
> substantially less than 80 columns. Doin
On Mon, 5 Aug 2019 12:25:25 +0100
Will Deacon wrote:
> This can be read as "subtract 144 bytes (32*4 + 16) from the stack pointer,
> write the frame record there and then update the stack pointer to point at the
> bottom of the newly allocated stack", which means that the array 'a[32]' sits
> dir
On Thu, Aug 01, 2019 at 09:37:49AM -0400, Phil Auld wrote:
> Enabling WARN_DOUBLE_CLOCK in /sys/kernel/debug/sched_features causes
ISTR there were more issues; but it sure is good to start picking them
off.
> warning to fire in update_rq_clock. This seems to be caused by onlining
> a new fair sch
On Mon, 05 Aug 2019 14:03:55 +0200,
Luca Coelho wrote:
>
> On Mon, 2019-08-05 at 13:10 +0300, Luca Coelho wrote:
> > On Mon, 2019-08-05 at 12:05 +0200, Takashi Iwai wrote:
> > > On Mon, 05 Aug 2019 11:53:33 +0200,
> > > Luca Coelho wrote:
> > > > On Mon, 2019-08-05 at 12:48 +0300, Luca Coelho wrot
Commit-ID: 91d2a812dfb98b3b4dad661529c33bc38d303461
Gitweb: https://git.kernel.org/tip/91d2a812dfb98b3b4dad661529c33bc38d303461
Author: Waiman Long
AuthorDate: Tue, 25 Jun 2019 10:39:13 -0400
Committer: Peter Zijlstra
CommitDate: Tue, 6 Aug 2019 12:49:15 +0200
locking/rwsem: Make hando
On Sat, Aug 3, 2019 at 3:34 PM Ramon Fried wrote:
> From: Stefan Wahren
>
> The user space like gpioinfo only see the GPIO usage but not the
> MUX usage (e.g. I2C or SPI usage) of a pin. As a user we want to know which
> pin is free/safe to use. So take the MUX usage of strict pinmux controllers
Adding the devicetree binding documentation for the Amlogic temperature
sensor found in the Amlogic Meson G12 SoCs.
the G12A and G12B SoCs are supported.
Signed-off-by: Guillaume La Roque
---
.../bindings/thermal/amlogic,thermal.yaml | 54 +++
1 file changed, 54 insertions(+
Amlogic G12A and G12B SoCs integrate two thermal sensors
with the same design.
One is located close to the DDR controller and the other one is
located close to the PLLs (between the CPU and GPU).
The calibration data for each of the thermal sensors instance is
stored in a different location within
Add myself as maintainer for Amlogic Thermal driver.
Signed-off-by: Guillaume La Roque
Reviewed-by: Neil Armstrong
---
MAINTAINERS | 9 +
1 file changed, 9 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index fb2b12f75c37..299f27d11058 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@
Add minimal thermal zone for two temperature sensor
One is located close to the DDR and the other one is
located close to the PLLs (between the CPU and GPU)
Signed-off-by: Guillaume La Roque
---
.../boot/dts/amlogic/meson-g12a-sei510.dts| 56 +++
1 file changed, 56 insertions
Add minimal thermal zone for two temperature sensor
One is located close to the DDR and the other one is
located close to the PLLs (between the CPU and GPU)
Signed-off-by: Guillaume La Roque
---
.../boot/dts/amlogic/meson-g12b-odroid-n2.dts | 60 +++
1 file changed, 60 insertions
Add cpu and ddr temperature sensors for G12 Socs
Signed-off-by: Guillaume La Roque
Reviewed-by: Martin Blumenstingl
---
.../boot/dts/amlogic/meson-g12-common.dtsi| 20 +++
1 file changed, 20 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-g12-common.dtsi
b/arc
This patchs series add support of New Amlogic temperature sensor and minimal
thermal zone for SEI510 and ODROID-N2 boards.
First implementation was doing on IIO[1] but after comments i move on thermal
framework.
Formulas and calibration values come from amlogic.
Changes since v2:
- fix yaml do
Commit-ID: fce45cd41101f1a9620267146b21f09b3454d8db
Gitweb: https://git.kernel.org/tip/fce45cd41101f1a9620267146b21f09b3454d8db
Author: Davidlohr Bueso
AuthorDate: Sun, 28 Jul 2019 21:47:35 -0700
Committer: Peter Zijlstra
CommitDate: Tue, 6 Aug 2019 12:49:15 +0200
locking/rwsem: Check
Commit-ID: 5f35d5a66b3ec62cb5ec4ec2ad9aebe2ac325673
Gitweb: https://git.kernel.org/tip/5f35d5a66b3ec62cb5ec4ec2ad9aebe2ac325673
Author: Mukesh Ojha
AuthorDate: Wed, 31 Jul 2019 20:35:03 +0530
Committer: Peter Zijlstra
CommitDate: Tue, 6 Aug 2019 12:49:16 +0200
locking/mutex: Make __mut
Commit-ID: a037d269221c0ae15f47046757afcbd1a7177bbf
Gitweb: https://git.kernel.org/tip/a037d269221c0ae15f47046757afcbd1a7177bbf
Author: Mukesh Ojha
AuthorDate: Wed, 31 Jul 2019 20:35:04 +0530
Committer: Peter Zijlstra
CommitDate: Tue, 6 Aug 2019 12:49:16 +0200
locking/mutex: Use mutex
Add devicetree binding for IMX290 CMOS image sensor.
Signed-off-by: Manivannan Sadhasivam
Reviewed-by: Rob Herring
---
.../devicetree/bindings/media/i2c/imx290.txt | 51 +++
1 file changed, 51 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/i2c/imx290.
Hello,
This patchset adds support for IMX290 CMOS image sensor from Sony.
Sensor can be programmed through I2C and 4-wire interface but the
current driver only supports I2C interface. Also, the sensor is
capable of outputting frames in following 3 interfaces:
* CMOS logic parallel SDR output
* Lo
Add driver for Sony IMX290 CMOS image sensor driver. The driver only
supports I2C interface for programming and MIPI CSI-2 for sensor output.
Signed-off-by: Manivannan Sadhasivam
---
drivers/media/i2c/Kconfig | 11 +
drivers/media/i2c/Makefile | 1 +
drivers/media/i2c/imx290.c | 845
Add MAINTAINERS entry for Sony IMX290 CMOS image sensor driver.
Signed-off-by: Manivannan Sadhasivam
---
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index d0ed735994a5..27e4c1f57b61 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -14669,6 +1466
From: Dan Carpenter
> Sent: 06 August 2019 12:53
> On Mon, Aug 05, 2019 at 10:33:29PM -0300, Jose Carlos Cazarin Filho wrote:
> > Fix checkpath warning:
> > WARNING: Unnecessary typecast of c90 int constant
> >
> > Signed-off-by: Jose Carlos Cazarin Filho
> > ---
> > Hello all!
> > This is my fi
On Tue, Aug 6, 2019 at 3:04 PM Linus Walleij wrote:
> On Sat, Aug 3, 2019 at 3:34 PM Ramon Fried wrote:
>
> > From: Stefan Wahren
> >
> > The user space like gpioinfo only see the GPIO usage but not the
> > MUX usage (e.g. I2C or SPI usage) of a pin. As a user we want to know which
> > pin is fr
> -Original Message-
> From: Cornelia Huck
> Sent: Tuesday, August 6, 2019 1:59 PM
> To: Parav Pandit
> Cc: k...@vger.kernel.org; wankh...@nvidia.com; linux-
> ker...@vger.kernel.org; alex.william...@redhat.com; c...@nvidia.com
> Subject: Re: [PATCH 2/2] vfio/mdev: Removed unused and r
201 - 300 of 1002 matches
Mail list logo
