Signed-off-by: Mariusz Kozlowski <[EMAIL PROTECTED]>
drivers/char/drm/drm_sman.c | 9108 -> 9094 (-14 bytes)
drivers/char/drm/drm_sman.o | 104466 -> 103946 (-520 bytes)
drivers/char/drm/drm_sman.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
--- linux-2.6.23-rc3-mm1.orig
Signed-off-by: Mariusz Kozlowski <[EMAIL PROTECTED]>
drivers/char/drm/drm_stub.c | 7731 -> 7728 (-3 bytes)
drivers/char/drm/drm_stub.o | 110301 -> 111354 (+1053 bytes)
drivers/char/drm/drm_stub.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-2.6.23-rc3-mm1.orig/drivers/ch
Signed-off-by: Mariusz Kozlowski <[EMAIL PROTECTED]>
drivers/char/drm/i810_dma.c | 37542 -> 37480 (-62 bytes)
drivers/char/drm/i810_dma.o | 150664 -> 149996 (-668 bytes)
drivers/char/drm/i810_dma.c |9 -
1 file changed, 4 insertions(+), 5 deletions(-)
--- linux-2.6.23-rc3-mm1.orig
Signed-off-by: Mariusz Kozlowski <[EMAIL PROTECTED]>
drivers/char/drm/i830_dma.c | 41269 -> 41212 (-57 bytes)
drivers/char/drm/i830_dma.o | 157920 -> 157480 (-440 bytes)
drivers/char/drm/i830_dma.c |6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
--- linux-2.6.23-rc3-mm1.orig/dr
Signed-off-by: Mariusz Kozlowski <[EMAIL PROTECTED]>
drivers/char/drm/i915_dma.c | 22680 -> 22623 (-57 bytes)
drivers/char/drm/i915_dma.o | 134192 -> 133704 (-488 bytes)
drivers/char/drm/i915_dma.c |6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
--- linux-2.6.23-rc3-mm1.orig/dr
Signed-off-by: Mariusz Kozlowski <[EMAIL PROTECTED]>
drivers/char/drm/mga_dma.c | 30418 -> 30253 (-165 bytes)
drivers/char/drm/mga_dma.o | 140668 -> 140304 (-364 bytes)
drivers/char/drm/mga_dma.c | 14 +-
1 file changed, 5 insertions(+), 9 deletions(-)
--- linux-2.6.23-rc3-mm1.o
This patch does drm_calloc to drm_zalloc conversion. Also it
seems that unpatched version allocated wrong nr of bytes.
drm_i915_vbl_swap_t *vbl_swap;
...
sizeof(vbl_swap) vs. sizeof(*vbl_swap)
No?
Please review.
Signed-off-by: Mariusz Kozlowski <[EMAIL PROTECTED]>
drivers/char/drm/i915_irq.
Signed-off-by: Mariusz Kozlowski <[EMAIL PROTECTED]>
drivers/char/drm/i915_mem.c | 9842 -> 9808 (-34 bytes)
drivers/char/drm/i915_mem.o | 114556 -> 114464 (-92 bytes)
drivers/char/drm/i915_mem.c |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
--- linux-2.6.23-rc3-mm1.orig/drivers/c
Signed-off-by: Mariusz Kozlowski <[EMAIL PROTECTED]>
drivers/char/drm/radeon_cp.c | 62519 -> 62461 (-58 bytes)
drivers/char/drm/radeon_cp.o | 160564 -> 160596 (+32 bytes)
drivers/char/drm/radeon_cp.c |5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
--- linux-2.6.23-rc3-mm1.orig/d
Signed-off-by: Mariusz Kozlowski <[EMAIL PROTECTED]>
drivers/char/drm/r128_cce.c | 25912 -> 25792 (-120 bytes)
drivers/char/drm/r128_cce.o | 133640 -> 133468 (-172 bytes)
drivers/char/drm/r128_cce.c | 11 ---
1 file changed, 4 insertions(+), 7 deletions(-)
--- linux-2.6.23-rc3-mm1.o
The initialization in for loop can be removed as the SET_AGE macro
set the age struct and other members to zero.
Signed-off-by: Mariusz Kozlowski <[EMAIL PROTECTED]>
drivers/char/drm/savage_bci.c | 31888 -> 31634 (-254 bytes)
drivers/char/drm/savage_bci.o | 138936 -> 138984 (+48 bytes)
driver
Signed-off-by: Mariusz Kozlowski <[EMAIL PROTECTED]>
drivers/char/drm/radeon_mem.c | 7711 -> 7677 (-34 bytes)
drivers/char/drm/radeon_mem.o | 115484 -> 115396 (-88 bytes)
drivers/char/drm/radeon_mem.c |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
--- linux-2.6.23-rc3-mm1.orig/dri
Signed-off-by: Mariusz Kozlowski <[EMAIL PROTECTED]>
drivers/char/drm/via_map.c | 3449 -> 3439 (-10 bytes)
drivers/char/drm/via_map.o | 110028 -> 110488 (+460 bytes)
drivers/char/drm/via_map.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- linux-2.6.23-rc3-mm1.orig/drivers/c
Signed-off-by: Mariusz Kozlowski <[EMAIL PROTECTED]>
drivers/char/drm/sis_drv.c | 3249 -> 3239 (-10 bytes)
drivers/char/drm/sis_drv.o | 104756 -> 105460 (+704 bytes)
drivers/char/drm/sis_drv.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- linux-2.6.23-rc3-mm1.orig/drivers/c
Hi folks,
For some reason, every time I create a virtual interface (using tun),
the interface immediately generates an IGMPv3 Join packet for group
224.0.0.251, which (according to Google) is Multicast DNS.
This packet is generated automatically and consistently. I'm wondering
why this should be
m
On Tue, 7 Aug 2007 00:30:36 -0400, "Kyle Moffett" <[EMAIL PROTECTED]>
said:
> On Aug 06, 2007, at 19:37:47, Adam M wrote:
> > Hi folks,
> >
> > For some reason, every time I create a virtual interface (using
> > tun), the interface immediately generates
Hi Con,
Con Kolivas wrote:
Would some -ck user on the mailing list like to perform a set of
interbench benchmarks? They're pretty straight forward to do; see:
Here are my results for AMD 3200+ (2.2Ghz, uniprocessor), 1gb RAM, 10,000RPM
SATA drive after clean boots into runlevel 1.
2.6.19-ck
In brief: Adding entropy by writing to /dev/[u]random doesn't appear
to be working. I am aware that the reported available entropy (via
/proc/sys/kernel/random/entropy_avail) will not increase; the symptom
is /dev/random keeps spitting out the same numbers.
I have two embedded boards (one ARM, o
On 5/29/07, Theodore Tso <[EMAIL PROTECTED]> wrote:
On Tue, May 29, 2007 at 12:53:10PM +0100, M Macnair wrote:
Ok, so this is telling me a couple of things. First of all, if you're
only getting three outputs, it means that you don't have any
peripherals feeding entropy into the
On 5/29/07, Pavel Machek <[EMAIL PROTECTED]> wrote:
Hi!
> > I have two embedded boards (one ARM, one PowerPC), running two
> > different versions of 2.6. They have no hard drives, keyboards or
> > mice. They each have a NIC, but I understand these make no
> > contribution to the entropy pool.
On 29 May 2007 18:58:59 +0200, Andi Kleen <[EMAIL PROTECTED]> wrote:
"M Macnair" <[EMAIL PROTECTED]> writes:
>
> Many distros ship with an init script that saves and restores the
> entropy pool on startup and shutdown. The bit that interests me that
> is
Hi everybody,
I have a question concerning Ingo Molnar's realtime preempt patch.
This patch is great go get low latency on timer threads and a really
good real time behaviour.
I want to connect an external, embedded device via Ethernet (UDP/IP)
to my Linux PC. This communication should be in real
Hello Con,
Con Kolivas wrote:
This patchset is designed to improve system responsiveness and interactivity.
It is configurable to any workload but the default -ck patch is aimed at the
desktop and -cks is available with more emphasis on serverspace.
I have used SD for the first time with this
ke it and you will include it in kernel.
Or, if not, maybe this patch will start some debate regarding
the current insufficient limit of 255 loop devices.
Tomas M
slax.org
--- linux/drivers/block/loop_old.c 2007-02-04 18:44:54.0 +
+++ linux/drivers/block/loop.c 2007-03-22 08:31:55.00
n kernel
while there is no reason for it at all?"
My patch simply removes the hardcoded limitation.
Tomas M
slax.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.
) 1024 and which would be ACCEPTED to mainline kernel
any soon?
I'm offering MONEY for this task.
Let's say $256 ;-)
I hope I didn't offend anyone by this offer.
Tomas M
slax.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
e, I'm just used
to pay for others' time, I hope it doesn't offend you.
Thank you for your consideration.
Tomas M
slax.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
dm-loop, people would need kernel patch *and* userspace utilities.
So, from my point of view, it would be better to fix/enhance Linux's loop.
Tomas M
slax.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTE
he memory, which would be allocated anyway.
Thank you for your consideration
Tomas M
slax.org
--- linux/drivers/block/loop.c_old 2007-03-23 14:27:04.0 +
+++ linux/drivers/block/loop.c 2007-03-23 14:31:18.098458759 +
@@ -1358,7 +1358,7 @@
* And now the modules
t? In this case, this is unusable for many as it is not
backward compatible with old loop.c, am I correct?
Tomas M
slax.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.
[1] Summary:
Kernel Reports Oops: 0002 [1] SMP and the system becomes unstable
[2] Full Description:
Sometimes, randomly i get this Oops message and the system becomes
unstable. By unstable i mean all applications segmentation faults when i
execute (after the Oops). Sometimes X crashes, sometim
oot is needed!
On Tue, 2007-04-24 at 12:39 -0400, Chuck Ebbert wrote:
> Thiago M. Sayão wrote:
> > Sometimes, randomly i get this Oops message and the system becomes
> > unstable. By unstable i mean all applications segmentation faults when i
> > execute (after the Oops). Sometim
-0400, Chuck Ebbert wrote:
> Thiago M. Sayão wrote:
> > I also got this error yesterday which seems related:
> >
> > Bad pagetable: 001d [1] SMP
> > Bad pagetable: 0009 [2] SMP
> >
>
> You may have a hardware problem. Did you test the memory?
>
-
To
Just tested the memory again and some errors showed up. I swear that
they didn't appear the last time i tested. Sorry.
Thanks
Thiago.
On Wed, 2007-04-25 at 18:24 -0400, Chuck Ebbert wrote:
> Thiago M. Sayão wrote:
> > I also got this error yesterday which seems related:
> >
order to use more loops with 'mount':
$ losetup /dev/loop1000 file
$ mount /dev/loop1000 /mntpnt
I hope these binaries will be fixed soon.
Tomas M
slax.org
diff --git a/drivers/block/loop.c b/drivers/block/loop.c
index 6b5b642..7db2c38 100644
--- a/drivers/block/loop.c
+++ b/drivers/block/l
Hi,
I've seen this around, and have heard about it in forums and else-where,
could somebody enlighten me with more information or with experiences
they have had. Looks like kswapd begins to eat CPU dramatically till the
box eventually locks up.
Thanks,
Pedram
-
To unsubscribe from this list: se
Do i submit that here?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
How about this one? Am I doing it right now?
If not, please try to explain more to me what I am
doing wrong.
@@ -4760,7 +4760,7 @@
for (i = 0; i < NR_CARDS; i++) {
/* look for a Cyclades card by vendor and device id */
while ((device_id = cy_pci_dev_id[dev_
parameter is used at all, there will be unlimited amount of
loops. Simply clever :)
This will make it _completely_ backward-compatible, with very small code
change I guess.
Just my two cents.
Thank you for reading so far.
Tomas M
slax.org
-
To unsubscribe from this list: send the line "
ignored, rather it should
have the same function like before - to limit the loop driver so if you
use max_loop=10 for example, it should not allow loop.c to create more
than 10 loops.
Tomas M
slax.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the bo
ion.
Tomas M
slax.org
Ken Chen wrote:
On 3/31/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
> Yes, the distros do, and they recommend it to their users a lot.
Thanks. In that case I think we should retain the max_loop module
parameter
for now.
Ken, when you respin that pat
Hi,
I have two processors on the same die. One is an ARM processor running
linux and another is a non-ARM processor running linux operating
system (Proprietary Proc). We do not have any medium like Network
Interface or PCI or USB running between the two processors, except 1GB
of shared memory.
W
From: Suniel Mahesh
Earlier commit:
"spi: Pick spi bus number from Linux idr or spi alias"
(SHA1:9b61e302210eba55768962f2f11e96bb508c2408)
has introduced some checkpatch issues. As pointed by
Lukas Wunner this patch does the following:
- remove whitespaces
- fix warnings, suspect code indent for
From: Suniel Mahesh
spi framework should allocate bus number dynamically either
via Linux IDR or spi alias for master drivers. This patch deletes
code pertaining to manual allocation of spi bus number in spi omap2
master driver.
Signed-off-by: Suniel Mahesh
Signed-off-by: Karthik Tummala
Teste
From: Suniel Mahesh
Bool tests don't need comparisons.
This fixes the following coccinelle warning:
WARNING: Comparison of bool to 0/1
Signed-off-by: Suniel Mahesh
---
Note:
- Patch was tested and built(ARCH=arm) on latest
linux-next.
- No build issues reported, however it was not
tested o
From: Suniel Mahesh
This fixes the following coccinelle warning:
WARNING: return of 0/1 in function 'ssi_is_hw_key' with return type bool.
Signed-off-by: Suniel Mahesh
---
Note:
- Patch was tested and built(ARCH=arm) on latest
linux-next.
- No build issues reported, however it was not
teste
From: Suniel Mahesh
Comparision operator "equal to" not required on a variable
"foo" of type "bool". Bool has only two values, can be used
directly or with logical not.
This fixes the following coccinelle warning:
WARNING: Comparison of bool to 0/1
Signed-off-by: Suniel Mahesh
---
Changes for
From: Suniel Mahesh
Return "false" instead of 0.
This fixes the following coccinelle warning:
WARNING: return of 0/1 in function 'ssi_is_hw_key' with return type bool.
Signed-off-by: Suniel Mahesh
---
Changes for v2:
- Changed the commit log to give a more accurate description
of the changes
From: Suniel Mahesh
This fixes the following coccinelle warning:
WARNING: return of 0/1 in function 'ssi_is_hw_key' with return type bool.
return "false" instead of 0.
Signed-off-by: Suniel Mahesh
---
Changes for v3:
- Changed the commit log even more to give an accurate
description of the c
Good day dear, i hope this mail meets you well? I know this may seem
inappropriate so
i ask for your forgiveness but i wish to get to know you better, if I may be so
bold.
I consider myself an easy-going man, adventurous, honest and fun loving person
but I
am currently looking for a relationsh
2. If appropriate: referrals to people who might be open to helping
us work through this issue as a paid consulting project.
Thanks in advance!
Kind regards,
Pete M
patches were never merged (some since April). Yong Zhi and
> Naveen M, can you help resubmit a patchset that aligns the handling of
> buttons for DA7219-based devices?
>
> Thanks!
>
>
Sure Pierre, we will soon post the change for all DA7219 based boards.
Thanks
> >
> &
Hi Al,
Today's linux-next merge of the vfs tree got a conflict in fs/namei.c between
commit 890458a43dbd ("path: New helpers path_get_pin/path_put_unpin for path
pin") from the nfsd tree and commit 894bc8c4662b ("namei: remove restrictions
on nesting depth") from the vfs tree.
I fixed it up (see
On Tue, 22 May 2018 at 19:44, Geert Uytterhoeven
wrote:
> Hi Michel,
> On Tue, May 22, 2018 at 12:01 PM, Michel Pollet
> wrote:
> > This adds the constants necessary to use the renesas,rzn1-clocks driver.
> >
> > Signed-off-by: Michel Pollet
> Thanks for your patch!
> > ---
> > include/dt-b
Hi Rob,
On Tue, 22 May 2018 at 17:09, Rob Herring wrote:
> On Tue, May 22, 2018 at 11:01:23AM +0100, Michel Pollet wrote:
> > The Renesas RZ/N1 Family (Part #R9A06G0xx) requires a driver
> > to provide the SoC clock infrastructure for Linux.
> >
> > This documents the driver bindings.
> >
> > Si
Morning Geert,
On Wed, 23 May 2018 at 08:26, Geert Uytterhoeven
wrote:
> Hi Michel,
> On Wed, May 23, 2018 at 8:44 AM, M P wrote:
> > On Tue, 22 May 2018 at 19:44, Geert Uytterhoeven
> > wrote:
> >> On Tue, May 22, 2018 at 12:01 PM, Michel Pollet
> >> w
Hi Geert,
On Wed, 23 May 2018 at 10:12, Geert Uytterhoeven
wrote:
> Hi Michel,
> On Tue, May 22, 2018 at 12:01 PM, Michel Pollet
> wrote:
> > This adds the Renesas RZ/N1D (Part #R9A06G032) SoC bare
> > bone support.
> >
> > This currently only handles generic parts (gic, architected timer)
> >
Hi Geert,
On Wed, 23 May 2018 at 12:18, Geert Uytterhoeven
wrote:
> Hi Michel,
> On Wed, May 23, 2018 at 11:20 AM, M P wrote:
> > On Wed, 23 May 2018 at 10:12, Geert Uytterhoeven
> > wrote:
> >> On Tue, May 22, 2018 at 12:01 PM, Michel Pollet
> >> wrote
No problem. In a previous patch I had one for each item, but I thought
it could be packed in a single one - and avoid '[PATCH n/m]'.
Thanks.
On 3/12/19, Dan Carpenter wrote:
> On Tue, Mar 12, 2019 at 11:39:13AM -0300, Guilherme T Maeoka wrote:
>> From: Guilherme T Maeoka
>
My Greeting, Did you receive the letter i sent to you. Please answer me.
Best Regard,
Maureen magoko.
在 2020/7/28 23:54, Joe Perches 写道:
On Tue, 2020-07-28 at 21:38 +0800, wanghai (M) wrote:
Thanks for your explanation. I got it.
Can it be modified like this?
[]
+++ b/drivers/net/ethernet/cavium/liquidio/octeon_device.c
@@ -1152,11 +1152,8 @@ octeon_register_dispatch_fn(struct
On 2020/7/31 16:12, Herbert Xu wrote:
On Sat, Jul 25, 2020 at 11:44:36AM +0800, Yang Shen wrote:
From: Shukun Tan
Update debugfs interface parameters
Signed-off-by: Shukun Tan
Signed-off-by: Yang Shen
Reviewed-by: Zhou Wang
---
drivers/crypto/hisilicon/zip/zip_main.c | 55 +
On 2020/7/31 16:28, Herbert Xu wrote:
On Sat, Jul 25, 2020 at 02:06:46PM +0800, Yang Shen wrote:
This patchset fix some bug:
patch 1:clear the debug registers when remove driver
patch 2:intercept invalid input when using decompress
patch 3:replace the return value '-EBUSY' with '-EAGAIN' when
On 2020/8/5 14:04, Markus Elfring wrote:
Thanks for your review. There is only one error branch need to do
something uninit. So I think the jump is not necessary and will
affect code reading.:)
How does this concern fit to the Linux coding style?
https://git.kernel.org/pub/scm/linux/kernel/g
在 2020/8/6 22:23, Timur Tabi 写道:
On 8/6/20 9:06 AM, Wang Hai wrote:
In emac_clks_phase1_init() of emac_probe(), there may be a situation
in which some clk_prepare_enable() succeed and others fail.
If emac_clks_phase1_init() fails, goto err_undo_clocks to clean up
the clk that was successfully
On 2020/8/6 15:23, Markus Elfring wrote:
Would you become interested to look if any other software components
would be similarly affected?
Yeah, I'll check the rest and fix if any and send those in a
clean up patch.
Thanks,
Yang
在 2020/8/7 21:38, Timur Tabi 写道:
On 8/6/20 8:54 PM, wanghai (M) wrote:
Thanks for your suggestion. May I fix it like this?
Yes, this is what I had in mind. Thanks.
Acked-by: Timur Tabi
.
Thanks for your ack. I just sent a new patch.
"[PATCH net] net: qcom/emac: add m
在 2020/8/19 3:54, David Miller 写道:
From: Wang Hai
Date: Tue, 18 Aug 2020 21:44:04 +0800
Fix the missing free_netdev() before return from
gemini_ethernet_port_probe() in the error handling case.
Fixes: 4d5ae32f5e1e ("net: ethernet: Add a driver for Gemini gigabit ethernet")
Reported-by: Hulk
在 2020/11/24 11:22, xuqiang (M) 写道:
在 2020/11/24 3:52, Andrew Morton 写道:
On Mon, 23 Nov 2020 13:13:59 + Xu Qiang
wrote:
when hardlockup_all_cpu_backtrace is on, and there are
a large number of cores in the system, it takes
a long time to output the hard deadlock logs of all cores
to
Our recent test shows that the idle value of /proc/stat can decrease.
Is this an unreported bug? or it has been reported and the solution is
waiting to get merged.
The results of the two readings from /proc/stat are shown as below, the
interval between the two readings is 150 ms:
cat /proc/s
Hello there,
Good day. I sent you an email a few days ago but I did not
receive a reply. I am not sure if you got that email or not. I am
Muhammad Faraz. I got your contact from an online business
directory and I am contacting you because I have a proposition
that could be of great interest to
Hi Eric,
在 2021/3/22 17:05, Auger Eric 写道:
Hi Chenxiang,
On 3/22/21 7:40 AM, chenxiang (M) wrote:
Hi Eric,
在 2021/3/20 1:36, Auger Eric 写道:
Hi Chenxiang,
On 3/4/21 8:55 AM, chenxiang (M) wrote:
Hi Eric,
在 2021/2/24 4:56, Eric Auger 写道:
Implement domain-selective, pasid selective and
Hi Eric,
在 2021/3/20 1:36, Auger Eric 写道:
Hi Chenxiang,
On 3/4/21 8:55 AM, chenxiang (M) wrote:
Hi Eric,
在 2021/2/24 4:56, Eric Auger 写道:
Implement domain-selective, pasid selective and page-selective
IOTLB invalidations.
Signed-off-by: Eric Auger
---
v13 -> v14:
- Add dom
On Wed, 17 Mar 09:54, Lin Feng wrote:
After more than one month testing, we find that it is not suitable to process
e820 directly in kexec to place the kernel code. Some regions, like tmplog
and memattr tables, are not marked as reserved in e820.
Take tmplog, for example, the memory of table is m
On 2021/3/26 17:14, Herbert Xu wrote:
On Fri, Mar 19, 2021 at 03:33:07PM +0800, Yang Shen wrote:
+const struct hisi_zip_sqe_ops hisi_zip_ops_v2 = {
+ .sqe_type = 0x3,
+ .fill_addr = hisi_zip_fill_addr,
+ .fill_buf_size = hisi_zip_fill_buf
Hi,
在 2021/2/12 18:50, Joerg Roedel 写道:
On Tue, Feb 09, 2021 at 06:06:20PM +0530, Sai Prakash Ranjan wrote:
diff --git a/include/linux/iommu.h b/include/linux/iommu.h
index 5e7fe519430a..6064187d9bb6 100644
--- a/include/linux/iommu.h
+++ b/include/linux/iommu.h
@@ -87,6 +87,7 @@ struct iommu_
There is a syntax problem with this patch, please ignore it!
在 2020/11/18 18:39, Wang Hai 写道:
Fix to return a negative error code from the error handling
case instead of 0, as done elsewhere in this function.
Fixes: 47a18c42d992 ("android/ion: userspace test utility for ion buffer
sharing")
Re
在 2020/11/20 2:22, Julian Anastasov 写道:
Hello,
On Thu, 19 Nov 2020, Wang Hai wrote:
kmemleak report a memory leak as follows:
BUG: memory leak
unreferenced object 0x8880759ea000 (size 256):
comm "syz-executor.3", pid 6484, jiffies 4297476946 (age 48.546s)
hex dump (first 32 byte
[40163650] page_vma_mapped_walk+0x144/0x1e8
Thanks,
Krishna M
在 2020/11/24 3:52, Andrew Morton 写道:
On Mon, 23 Nov 2020 13:13:59 + Xu Qiang wrote:
when hardlockup_all_cpu_backtrace is on, and there are
a large number of cores in the system, it takes
a long time to output the hard deadlock logs of all cores
to the serial port. When the console_flush_
在 2020/11/24 9:22, Jakub Kicinski 写道:
On Sun, 22 Nov 2020 10:34:56 +0800 Wang Hai wrote:
kmemleak report a memory leak as follows:
unreferenced object 0x8880059c6a00 (size 64):
comm "ip", pid 23696, jiffies 4296590183 (age 1755.384s)
hex dump (first 32 bytes):
20 01 00 10 00 00
在 2020/12/4 16:40, Johan Hovold 写道:
On Fri, Dec 04, 2020 at 10:13:50AM +0800, Wang Hai wrote:
Add the missing unlock before return from function
gbaudio_dapm_free_controls() in the error handling case.
Fixes: 510e340efe0c ("staging: greybus: audio: Add helper APIs for dynamic audio
module")
在 2020/12/5 2:02, Vaibhav Agarwal 写道:
On Fri, Dec 4, 2020 at 2:10 PM Johan Hovold wrote:
On Fri, Dec 04, 2020 at 10:13:50AM +0800, Wang Hai wrote:
Add the missing unlock before return from function
gbaudio_dapm_free_controls() in the error handling case.
Fixes: 510e340efe0c ("staging: greyb
在 2020/12/3 18:34, Nikolay Aleksandrov 写道:
On 03/12/2020 03:03, Jakub Kicinski wrote:
On Tue, 1 Dec 2020 22:01:14 +0800 Wang Hai wrote:
If adding bridge sysfs fails, br->ifobj will be NULL, there is no
need to delete its non-existent sysfs when deleting the bridge device,
otherwise, it will c
在 2021/1/28 3:31, Linus Torvalds 写道:
[ Participants list changed - syzbot thought this was networking and
p9, but it really looks entirely like a slub internal bug. I left the
innocent people on the list just to let them know they are innocent ]
On Wed, Jan 27, 2021 at 6:27 AM syzbot
wrote:
> -Original Message-
> From: Arvind Sankar [mailto:nivedita...@gmail.com] On Behalf Of Arvind
> Sankar
> Sent: Wednesday, January 6, 2021 5:01 AM
> To: Ard Biesheuvel
> Cc: linfeng (M) ; Arvind Sankar
> ; Thomas Gleixner ; Ingo Molnar
> ; Borislav Petkov ; Huang
Ideally your commit subject would contain a verb, preferably in the present
tense.
I think simply "perf: Add PERF_SAMPLE_BRANCH_COND" would be clearer.
On Wed, 2013-16-10 at 06:56:48 UTC, Anshuman Khandual wrote:
> POWER8 PMU based BHRB supports filtering for conditional branches.
> This patch in
On Wed, 2013-16-10 at 06:56:49 UTC, Anshuman Khandual wrote:
> Enables conditional branch filter support for POWER8
> utilizing MMCRA register based filter and also invalidates
> a BHRB branch filter combination involving conditional
> branches.
>
> Signed-off-by: Anshuman Khandual
> ---
> arch/
interest on assurance of trust to
enable me give you full details and how this transaction will be executed. I
look forward to hear from you soon.
Best regards,
Mr. Zakan .M.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
I reported the bug as here:
https://bugzilla.kernel.org/show_bug.cgi?id=102531
I thought - maybe I could help fixing this, this doesn't seem as
difficult as writing a driver from scratch. Anyway, I'm completely new
to this stuff - could you aid me where I should start looking? The
firmware is all
Hello,
I need you to assist me claim and invest the sum of $50 Million(Fifty Million
US Dollars) in your Country.You will get 30% share out of the total fund for
your assistance.More details when i hear back from you.
Kind regards,
John
Hi Martin,
在 2019/2/9 7:13, Martin K. Petersen 写道:
John,
Just noticed this while inspecting the resulting complete diff:
static u32 get_prot_chk_msk_v3_hw(struct scsi_cmnd *scsi_cmnd)
{
unsigned char prot_flags = scsi_cmnd->prot_flags;
- if (prot_flags & SCSI_PROT_TRANSFER_PI)
Receive $39 Million for our mutual benefit.
On Mon, 7 Oct 2019 at 20:38, Linus Torvalds
wrote:
>
> On Mon, Oct 7, 2019 at 7:58 AM Francis M wrote:
> >
> > Attached is a JPEG of what I've been able to capture from the console.
> > I'm guessing it's probably not enough to go on, but hoping someone
>
在 2019/1/28 23:57, Christoph Hellwig 写道:
On Mon, Jan 28, 2019 at 03:36:58PM +, John Garry wrote:
As I understood, the problem is the scenario of calling
blk_mq_make_request()->bio_integrity_prep() where we then allocate a bio
integrity payload in calling bio_integrity_alloc().
In this ca
+cc Jens + linux-block
在 2019/1/24 21:43, chenxiang 写道:
In function blk_mq_make_request(), though data->cmd_flags will be
initialized with bio->opf, later bio->opf may be set as REQ_INTEGRITY
if enabled DIX. So need to use bio->opf instead of data->cmd_flags in
function blk_mq_rq_ctx_init(), or
On Mon, 24 Jun 2019 at 12:49, Jake M wrote:
>
> Hi,
>
> The box has crashed twice this week both times related to telegraf, we
> are running ZFS and attached is the kernel config.
>
> Any ideas?
>
> Description: Ubuntu 18.04.2 LTS
> Release: 18.04
> Codename:
.
Anurup M (7):
arm64: MAINTAINERS: hisi: Add hisilicon SoC PMU support
dt-bindings: perf: hisi: Add Devicetree bindings for Hisilicon SoC PMU
Documentation: perf: hisi: Documentation for HIP05/06/07 PMU event
counting.
perf: hisi: Update Kconfig for Hisilicon PMU support
perf: hisi: Add
From: Tan Xiaojun
Add Hisilicon HiP05/06/07 Djtag dts bindings for CPU and IO Die
Signed-off-by: Tan Xiaojun
Signed-off-by: Anurup M
---
.../devicetree/bindings/arm/hisilicon/djtag.txt| 41 ++
1 file changed, 41 insertions(+)
create mode 100644 Documentation
djtag
hw version.
- use devm_kzalloc.
- Remove DDRC changes in this series. As the DDRC PMU doesnot
depend on djtag it will be send separately.
v1
--
-Initial version with support for L3C, MN and DDRC event counters
-Djtag driver is used to access registers of L3 cache and MN.
Anurup M (7
101 - 200 of 1263 matches
Mail list logo
