Fixes a grammatical error in the output where the word 'to' was missing.
Signed-off-by: Anish Dabhane
---
tools/testing/selftests/cachestat/test_cachestat.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/cachestat/test_cachestat.c
b/too
On Tue, Oct 15, 2024 at 9:57 PM Mukesh Ojha wrote:
>
> Multiple call to glink_subdev_stop() for the same remoteproc can happen
> if rproc_stop() fails from Process-A that leaves the rproc state to
> RPROC_CRASHED state later a call to recovery_store from user space in
> Process B triggers rproc_tr
offset will always be positive number and adding
and comparing to the same variable 'size' will
always result in check being false always.
Remove this superfluous check.
Signed-off-by: anish kumar
---
drivers/remoteproc/remoteproc_elf_loader.c | 2 +-
1 file changed, 1 insertion(+),
Ran checkpatch and found these warnings. Fixed some of them in this patch.
a) Added a space before '='.
b) Removed the space before the tab.
Signed-off-by: Anish Udupa H
---
net/ipv4/route.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/net/ipv4/route.c
Ran checkpatch and found some warnings. Fixed some of them in this patch.
a) Added a new line after declarations.
b) Added * before each line in a multi-line comment and made sure that
they are aligned properly.
Signed-off-by: Anish Udupa H
---
net/ipv6/icmp.c | 15 ---
1 file
The * of the comment was not aligned properly. Ran checkpatch and
found the warning. Resolved it in this patch.
Signed-off-by: Anish Udupa
---
drivers/staging/qlge/qlge_main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/qlge/qlge_main.c b/drivers/staging
On Mon, Oct 5, 2015 at 1:27 PM, Andrew Morton wrote:
> On Mon, 5 Oct 2015 13:23:58 -0700 Anish Bhatt wrote:
>
>> alder32 was renamed to zlib_adler32 since before 2.6.11, update
>> the example accordingly. This code does not seem to have an
>> assigned maintainer.
>&
alder32 was renamed to zlib_adler32 since before 2.6.11, update
the example accordingly. This code does not seem to have an
assigned maintainer.
Signed-off-by: Anish Bhatt
---
include/linux/zutil.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/zutil.h b
alder32 was renamed to zlib_adler32 since before 2.6.11, this code
does not seem to have an assigned maintainer.
Signed-off-by: Anish Bhatt
---
include/linux/zutil.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/zutil.h b/include/linux/zutil.h
index
> -Original Message-
> From: Nicholas Krause [mailto:xerofo...@gmail.com]
> Sent: Thursday, September 3, 2015 10:44 AM
> To: jbottom...@odin.com
> Cc: h...@suse.de; micha...@cs.wisc.edu; da...@davemloft.net; Anish
> Bhatt; Hariprasad S; linux-s...@vger.kernel
> -Original Message-
> From: Nicholas Krause [mailto:xerofo...@gmail.com]
> Sent: Thursday, September 3, 2015 10:09 AM
> To: jbottom...@odin.com
> Cc: h...@suse.de; micha...@cs.wisc.edu; da...@davemloft.net; Anish
> Bhatt; Hariprasad S; linux-s...@vger.kernel
> -Original Message-
> From: Praveen Madhavan
> Sent: Friday, September 4, 2015 6:12 AM
> To: Anish Bhatt; Nicholas Krause; jbottom...@odin.com
> Cc: h...@suse.de; micha...@cs.wisc.edu; da...@davemloft.net;
> Hariprasad S; linux-s...@vger.kernel.org; linux-kern
> -Original Message-
> From: Nicholas Krause [mailto:xerofo...@gmail.com]
> Sent: Wednesday, September 2, 2015 10:36 AM
> To: jbottom...@odin.com
> Cc: h...@suse.de; micha...@cs.wisc.edu; da...@davemloft.net; Anish
> Bhatt; Hariprasad S; linux-s...@vger.kernel
Signed-off-by: Anish Bhatt
---
include/linux/zutil.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/zutil.h b/include/linux/zutil.h
index 6adfa9a..6636895 100644
--- a/include/linux/zutil.h
+++ b/include/linux/zutil.h
@@ -68,10 +68,10 @@ typedef uLong
Acked-by: Anish Bhatt --
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Mon, Mar 23, 2015 at 11:32 PM, Takashi Iwai wrote:
> At Mon, 23 Mar 2015 17:04:26 -0700,
> anish wrote:
>>
>> Hello,
>>
>> I was wondering if this patch is in any of the queue?
>
> I guess it's not. One of the reasons is that you don't know
Hello,
I was wondering if this patch is in any of the queue?
On Mon, Mar 2, 2015 at 3:16 PM, Anish Kumar wrote:
> This patch adds maintainer for maxim audio codecs.
> Signed-off-by: Anish Kumar
> ---
> MAINTAINERS | 7 +++
> 1 file changed, 7 insertions(+)
>
> diff
Is it picked up?
On Mon, Mar 2, 2015 at 3:16 PM, Anish Kumar wrote:
> This patch adds maintainer for maxim audio codecs.
> Signed-off-by: Anish Kumar
> ---
> MAINTAINERS | 7 +++
> 1 file changed, 7 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index
This patch adds maintainer for maxim audio codecs.
Signed-off-by: Anish Kumar
---
MAINTAINERS | 7 +++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 8bdd7a7..2128586 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -7387,6 +7387,13 @@ S: Supported
F
It got to the maintainer nevertheless. Thanks for bringing this to our notice
Paul, fix for this is already in the patchwork queue :
https://patchwork.ozlabs.org/patch/434279/
-Anish
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
Aah, ignore this please. Somehow I missed the two other recent mail chains
about this very thing, and my patch only covers part of it anyways.--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
c:551:19: note: 'jump' was declared here
struct jump_key *jump;
Signed-off-by: Anish Bhatt
---
scripts/kconfig/menu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/kconfig/menu.c b/scripts/kconfig/menu.c
index a26cc5d..584e0fc 100644
--- a/scripts/kconfig
linux-n...@vger.kernel.org; linux-kernel@vger.kernel.org; Anish Bhatt;
Christoph Hellwig; Karen Xie
Subject: linux-next: build failure after merge of the scsi tree
Hi James,
After merging the scsi tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
drivers/scsi
> -Original Message-
> From: Chuck Ebbert [mailto:cebbert.l...@gmail.com]
> Sent: Friday, September 26, 2014 3:01 PM
> To: Anish Bhatt
> Cc: linux-kernel@vger.kernel.org; x...@kernel.org; t...@linutronix.de;
> mi...@redhat.com; h...@zytor.com; sebast...@fds-team.de
instruction.
Further details can be seen here https://bugs.winehq.org/show_bug.cgi?id=33275
Signed-off-by: Anish Bhatt
Signed-off-by: Sebastian Lackner
---
arch/x86/kernel/cpu/common.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/cpu/common.c b/arch/x86/kernel/cpu
> > cc'ing Anish Bhatt.
> >
> He knows about it, as do David Miller and Randy Dunlap (who proposed it)
> [1].
> There just doesn't seem to be an agreement on how to fix the problem.
> A simple revert doesn't work anymore since there are multiple follow-up
&
. However, having bnx2fc/i
as built-in overrides CNIC's tristate from m to built-in (as they select
CNIC),
causing build issues. As far as I know, there is no way to control the state
that select sets.
-Anish
From: Randy Dunlap [rdun...@infradead.org]
Leaves only 1 warning still reproduceable :
(LIBFCOE && TCM_QLA2XXX) selects LIBFC which has unmet direct dependencies
(SCSI_LOWLEVEL && SCSI && SCSI_FC_ATTRS),
so maybe that needs a fix too ? All the other fcoe/scsi menu entries behave
as expected.
upposed to be
automatically resolved ?
-Anish
From: Randy Dunlap [rdun...@infradead.org]
Sent: Friday, September 19, 2014 3:21 PM
To: Guenter Roeck; Stephen Rothwell
Cc: linux-n...@vger.kernel.org; linux-kernel@vger.kernel.org; Anish Bhatt;
David S. Miller;
ed to previously select NET on it's own (via SCSI_NET_LINK), maybe this
is wrong too ?
-Anish
From: Guenter Roeck [groe...@gmail.com] on behalf of Guenter Roeck
[li...@roeck-us.net]
Sent: Friday, September 19, 2014 2:14 PM
To: Stephen Rothwell
C
> -Original Message-
> From: Michael Chan [mailto:mc...@broadcom.com]
> Sent: Tuesday, September 9, 2014 4:21 PM
> To: Anish Bhatt
> Cc: Randy Dunlap; eddie@broadcom.com; Jim Davis; Stephen Rothwell;
> linux-next; linux-kernel; David S. Miller; netdev; James Botto
ee BNX2 drivers unless CNIC is selected,
similar
for SCSI_NETLINK as well, not sure if there are any other implications.
-Anish--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://v
> Adding depends on IPV6 || IPV6=n doesn't work for SCSI_BNX2X_FCOE, but
> works for SCSI_BNX2_ISCSI?
It fixes the config issue for both, but with FCOE; make scripts will complain
about recursive dependencies with the following :
scripts/kconfig/conf --silentoldconfig Kconfig
net/Kconfig:5:erro
ble ipv6 code
in such a situation.
-Anish
From: Jim Davis [jim.ep...@gmail.com]
Sent: Tuesday, September 09, 2014 7:38 AM
To: Stephen Rothwell; linux-next; linux-kernel; Anish Bhatt;
mc...@broadcom.com; David S. Miller; netdev
Subject: randconfig build error w
Adding Casey who's actually incharge of this code and missing from the CC list
-Anish
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
One socket to bind them all
From: Aaron Lu
Sent: Jul 27, 2014 7:05 PM
To: Anish Bhatt
Cc: "David S. Miller" ;LKML;l...@01.org
Subject: [LKP] [cxgb4i] INFO: suspicious RCU usage. ]
FYI, we noticed the below changes on
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.
This is totally my bad. Already posted the fix some time ago.
N�r��yb�X��ǧv�^�){.n�+{zX����ܨ}���Ơz�&j:+v���zZ+��+zf���h���~i���z� �w���?�&�)ߢf��^jǫy�m��@A�a���
0��h���i
seems-very-vague guess.
-Anish
From: Joe Perches [j...@perches.com]
Sent: Tuesday, July 15, 2014 9:20 PM
To: Ethan Zhao
Cc: Anish Bhatt; a...@canonical.com; linux-kernel@vger.kernel.org;
ethan.ker...@gmail.com; joe@oracle.com
Subject: Re: [Bug report]
$lines[$linenr - 3] !~ /^[ +]\s*$Ident\s*:/) {
> + WARN("RETURN_VOID",
> + "void function return statements are not generally
> useful\n" . $hereprev);
> + }
> +
> # if statements using unnecessary pare
On 06/16/2014 07:00 PM, Joe Perches wrote:
> On Mon, 2014-06-16 at 17:44 -0700, Anish Bhatt wrote:
>> My code has multiple exit lables:
>> void function(void)
>> {
>> ...
>>
>> if (err1)
>> goto exit1;
>>
(err2);
}
The single tabbed return was required to prevent the good return & err1
messages cascading down. The extra exit label with a noop looks weird,
but is passing checkpatch.pl --strict, so I will go with that, thanks.
-Anish
--
To unsubscribe from this list: send the line "unsubscr
? goto labels
can't be directly used in place either
-Anish Bhatt
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read t
small suggestions regarding interrupt registration ( request_irq()) call:
1. instead of request_irq() call in probe function , i think interrupt
can be registered in dwceqos_open() call . since packet only come when
we make interface up( ifconfig up) .
2. in request_irq() thier is flag parameter ca
On Mon, Mar 24, 2014 at 2:33 AM, Arend van Spriel wrote:
> On 23/03/14 23:31, anish singh wrote:
>>
>> Many a time i have got a crash and it is difficult
>> to find out the exact function which crashed
>> because the crash stack doesn't show the "real&
Many a time i have got a crash and it is difficult
to find out the exact function which crashed
because the crash stack doesn't show the "real"
function because gcc inlines many functions when
ever it desires or when it optimizes for speed.
So i don't want gcc to inline any function instead
just c
On Thu, Dec 12, 2013 at 12:21 PM, Filipe David Manana
wrote:
> Hello,
>
> I have a list that is manipulated by several threads. Insert, remove
> and iteration are protected by a lock. Is the locking necessary too
> just for checking if the list is empty, i.e., is list_empty()
> atomic/safe to call
On Mon, Dec 9, 2013 at 11:27 PM, Daniel Lezcano
wrote:
> On 12/10/2013 07:33 AM, Alex Shi wrote:
>>
>> On 12/09/2013 10:17 PM, Daniel Lezcano wrote:
>>>
>>>
>>> Concerning the wake up of the cpu: the cpu disabled the irq and
>>> goes to sleep, it is up to the firmware to wake up the cpu when an
>>
On Sun, Nov 17, 2013 at 5:19 PM, 韩磊 wrote:
> when we delete,add,search,amend the list_head,should we use spinlock
> or rcu in case of conflicit to list_head???
There is no implicit locking when we use 'list' api's.You should explicitly
do that AFAIK.
>
> Thank you!
> --
> To unsubscribe from this
On Thu, Oct 10, 2013 at 5:57 PM, Steven Rostedt
(by way of Steven Rostedt ) (by way of Steven
Rostedt wrote:
>
> [ Resending, as somehow Claws email, removed the quotes from "H. Peter
> Anvin", and that prevented LKML from receiving this ]
>
> *** NOT FOR INCLUSION ***
>
> What this does
>
On Tue, Aug 13, 2013 at 5:59 AM, Steven Rostedt wrote:
> On Mon, 12 Aug 2013 15:18:16 -0700
> Shailaja Neelam wrote:
>
>> I am a high school student trying to become familiar with the
>> opensource process and linux kernel. This is my first submission to
>> the ITC mailing list.
>
> Hi Shailaja,
On Wed, Aug 7, 2013 at 2:36 PM, Linus Walleij wrote:
> This macro was invented by Mattias Nilsson for the usecase
> where you want to set a sequence of bits inside a n-bit
> word, while leaving the head and tail of the sequence all
> zeroes. For example:
>
> #include
>
> u16 mask = BITS(4, 12
On Tue, Jul 16, 2013 at 10:29 AM, Rusty Russell wrote:
> anish singh writes:
>> Hello Rusty,
>>
>> Right now I see so many places in the kernel
>> where we open code binary search implementations
>> such as search_extable implementations.
>>
>> ht
problem nor I see
any problem in current implementations but
if we can replace the large amount of code
would it not be a good reason to send a patch
for this?
anish
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kerne
On Fri, Jun 28, 2013 at 1:01 AM, Wim Van Sebroeck wrote:
> Hi Anish,
>
>> Certain watchdog drivers use a timer to keep kicking the watchdog at
>> a rate of 0.5s (HZ/2) untill userspace times out.They do this as
>> we can't guarantee that watchdog will be pinged fast e
On Fri, Jun 14, 2013 at 9:42 PM, Steven Rostedt wrote:
> On Fri, 2013-06-14 at 21:33 +0530, anish singh wrote:
>
>> May I know why we zeroed in on 1Hz? Is there any logical reason
>> or just because it is above 0Hz?
>> >
>
> We had to keep a tick. What number wou
Thanks Paul & Steve for replying.
On Fri, Jun 14, 2013 at 5:56 PM, Paul E. McKenney
wrote:
> On Fri, Jun 14, 2013 at 09:47:31AM +0530, anish singh wrote:
>> On Thu, Jun 13, 2013 at 10:46 PM, Steven Rostedt wrote:
>> > On Thu, 2013-06-13 at 21:51 +0530, anish singh wrote:
&g
On Thu, Jun 13, 2013 at 10:46 PM, Steven Rostedt wrote:
> On Thu, 2013-06-13 at 21:51 +0530, anish singh wrote:
>
>> > The concept behind full dynamic ticks is very easy. When you set a given
>> > CPU(s) to dynamic tick, when it only has a single task scheduled on that
&
On Thu, Jun 13, 2013 at 9:18 PM, Steven Rostedt wrote:
> On Thu, 2013-06-13 at 11:20 -0400, Don Zickus wrote:
>
>> I don't know enough about how full dynticks work to even present a
>> solution. But currently I was working with the Red Hat performance team
>> to enhance perf to help our customers
On Wed, Jun 12, 2013 at 7:09 AM, Chanwoo Choi wrote:
> From: Kishon Vijay Abraham I
>
> Added an API of_extcon_get_extcon_dev() to be used by drivers to get
> extcon device in the case of dt boot (this can be used instead of
> extcon_get_extcon_dev()).
>
> Signed-off-by: Kishon Vijay Abraham I
>
On Mon, Jun 10, 2013 at 9:08 PM, Russell King - ARM Linux
wrote:
Least I can do is to say "Thanks".
> On Mon, Jun 10, 2013 at 08:46:36PM +0530, anish singh wrote:
>> Probably a trivial question.I was wondering why this particular requirement
>> exists in the first place.
On Tue, Jun 4, 2013 at 3:42 AM, Russell King - ARM Linux
wrote:
> On Mon, Jun 03, 2013 at 02:11:59PM -0700, Stephen Boyd wrote:
>> On 06/03/13 02:39, Russell King - ARM Linux wrote:
>> > On Sat, Jun 01, 2013 at 11:39:41PM -0700, Stephen Boyd wrote:
>> >> +}
>> >> +
>> >> +void __init
>> >> +setup_
On Mon, Jun 10, 2013 at 11:21 AM, PINTU KUMAR wrote:
> Hi,
>
> I wanted to submit my first patch.
> But I have some confusion about the /scripts/checkpatch.pl errors.
>
> After correcting some checkpatch errors, when I run checkpatch.pl, it showed
> me 0 errors.
> But when I create patches are gi
On Thu, Jun 6, 2013 at 10:11 AM, Guenter Roeck wrote:
> On Thu, Jun 06, 2013 at 08:30:01AM +0530, anish singh wrote:
>> Hello Wim Van,
>> Can you look into below?
>>
> Please be patient. Wim tends to be busy.
Sorry, I will wait.
>
> Guenter
>
>> On W
Hello Wim Van,
Can you look into below?
On Wed, Jun 5, 2013 at 8:39 AM, anish singh wrote:
> Hello Wim Van Sabroeck,
> Can I get your inputs on this?
>
> On Tue, Jun 4, 2013 at 8:39 AM, anish singh
> wrote:
>> On Tue, Jun 4, 2013 at 3:55 AM, Guenter Roeck wrote:
>>&
Hello Wim Van Sabroeck,
Can I get your inputs on this?
On Tue, Jun 4, 2013 at 8:39 AM, anish singh wrote:
> On Tue, Jun 4, 2013 at 3:55 AM, Guenter Roeck wrote:
>> On Mon, Jun 03, 2013 at 10:23:04PM +0530, anish singh wrote:
>>> On Mon, Jun 3, 2013 at 8:57 PM, Guenter Roeck w
On Tue, Jun 4, 2013 at 3:55 AM, Guenter Roeck wrote:
> On Mon, Jun 03, 2013 at 10:23:04PM +0530, anish singh wrote:
>> On Mon, Jun 3, 2013 at 8:57 PM, Guenter Roeck wrote:
>> > On Sun, Jun 02, 2013 at 03:43:07PM +0530, anish kumar wrote:
>> >> Certain watchdog drive
On Mon, Jun 3, 2013 at 8:57 PM, Guenter Roeck wrote:
> On Sun, Jun 02, 2013 at 03:43:07PM +0530, anish kumar wrote:
>> Certain watchdog drivers use a timer to keep kicking the watchdog at
>> a rate of 0.5s (HZ/2) untill userspace times out.They do this as
>> we can't gu
any inputs?
On Sun, Jun 2, 2013 at 3:56 PM, anish singh wrote:
> On Sun, Jun 2, 2013 at 3:43 PM, anish kumar
> wrote:
>> Certain watchdog drivers use a timer to keep kicking the watchdog at
>> a rate of 0.5s (HZ/2) untill userspace times out.They do this as
>> we can&#
On Sun, Jun 2, 2013 at 3:43 PM, anish kumar wrote:
> Certain watchdog drivers use a timer to keep kicking the watchdog at
> a rate of 0.5s (HZ/2) untill userspace times out.They do this as
> we can't guarantee that watchdog will be pinged fast enough
> for all system loads, espe
cally small values).
As suggested by Wim Van Sebroeck & Guenter Roeck we should
add this functionality of individual watchdog drivers in the core
watchdog core.
Signed-off-by: anish kumar
---
drivers/watchdog/watchdog_dev.c | 34 +-
include/linux/w
Hi Guenter,
On Fri, May 31, 2013 at 3:32 AM, Guenter Roeck wrote:
> On Thu, May 30, 2013 at 11:59:28PM +0200, Wim Van Sebroeck wrote:
>> Hi Guenter,
>>
>> > On Tue, May 28, 2013 at 10:10:53AM +0200, Johannes Thumshirn wrote:
>> > > On Mon, May 27, 2013 at 08:25:54PM +0200, Wim Van Sebroeck wrote:
On Thu, May 30, 2013 at 2:04 PM, Jean Delvare wrote:
> Hi Rusty,
>
> Thanks for the fast and helpful reply.
>
> On Thu, 30 May 2013 11:53:10 +0530, anish singh wrote:
>> On Thu, May 30, 2013 at 6:24 AM, Rusty Russell wrote:
>> > Jean Delvare writes:
>> >
On Thu, May 30, 2013 at 6:24 AM, Rusty Russell wrote:
> Jean Delvare writes:
>> Hi Greg, Rusty,
>>
>> I have a question related to /sys/module and can't seem to find the
>> answer by myself so I hope you can explain.
>>
>> I noticed that /sys/module contains more than /proc/modules. At first I
>>
On Fri, May 24, 2013 at 11:11 PM, Axel Lin wrote:
> If none of the channels are supported, index is 0.
> Also ensure to return error code instead of 0 in goto second_mem_fail path.
>
> Signed-off-by: Axel Lin
Acked-by: anish kumar
I think anton would have already picked up.
>
On Mon, May 27, 2013 at 6:52 PM, Ming Lei wrote:
> On Mon, May 27, 2013 at 8:40 PM, anish singh
> wrote:
>> On Mon, May 27, 2013 at 5:53 PM, Takashi Iwai wrote:
>>> At Mon, 27 May 2013 17:26:22 +0530,
>>> anish singh wrote:
>>>>
>>>
On Mon, May 27, 2013 at 5:53 PM, Takashi Iwai wrote:
> At Mon, 27 May 2013 17:26:22 +0530,
> anish singh wrote:
>>
>> On Mon, May 27, 2013 at 4:00 PM, Ming Lei wrote:
>> > Generally there are only two drivers which don't need uevent to
>> > handle firmwar
On Mon, May 27, 2013 at 4:00 PM, Ming Lei wrote:
> Generally there are only two drivers which don't need uevent to
> handle firmware loading, so don't cache these firmwares during
Sorry but this statement confuses me i.e. "drivers which don't need
uevent to handle firmware loading". Does this mean
On Fri, May 24, 2013 at 1:14 PM, Jean Delvare wrote:
> Hi Anish, Mylène,
>
> On Fri, 24 May 2013 12:52:40 +0530, anish singh wrote:
>> On Fri, May 24, 2013 at 12:41 PM, Mylene Josserand
>> wrote:
>> > I have read that this function "i2c_smbus_write_byte_dat
On Fri, May 24, 2013 at 12:41 PM, Mylene Josserand
wrote:
> Hi all,
>
>
> I am learning how i2c is working and I read that, to write in an i2c
> register, I need to use the function "i2c_smbus_write_byte_data".
Only in case your device is smbus compliant.
> I wanted to know how the message are ha
On Thu, May 23, 2013 at 3:46 PM, Takashi Iwai wrote:
> At Thu, 23 May 2013 10:06:56 +0200,
> Takashi Iwai wrote:
>>
>> At Thu, 23 May 2013 15:45:32 +0800,
>> Ming Lei wrote:
>> >
>> > On Thu, May 23, 2013 at 11:39 AM, Dave Jones wrote:
>> > > > On 05/21/2013 04:03 PM, Dave Jones wrote:
>> > > >
On Tue, May 21, 2013 at 1:19 PM, Srivatsa S. Bhat
wrote:
> On 05/21/2013 11:04 AM, anish singh wrote:
>> On Mon, May 20, 2013 at 9:31 PM, Frederic Weisbecker
>> wrote:
>>> When the watchdog code is boot-disabled by the user, for example
>>> through the '
On Mon, May 20, 2013 at 9:31 PM, Frederic Weisbecker wrote:
> When the watchdog code is boot-disabled by the user, for example
> through the 'nmi_watchdog=0' boot option, the setup() callback of
> the watchdog kthread requests to park the task, and that until the
> user later re-enables the watchd
On Tue, May 7, 2013 at 1:45 PM, Chanho Min wrote:
> In bitmap_find_free_region, If we skip the all-ones words and find bits
> in a not-all-ones word, we can improve performance of it.
>
> For example, If bitmap_find_free_region() is called with order=0, First,
> It scans bitmap array by the increm
Hello Vijay,
Below I will try my best to answer.
On Wed, Mar 20, 2013 at 8:23 PM, Vijay Dixit wrote:
> Hello,
>
> I am new to the Kernel-Mailing list. I am not subscribed at the moment
> and would really appreciate it, if I can be CC'd for all the
> reply/responses for my question.
>
>
> I have
Commit-ID: b66a2356d7108a15b8b5c9b8e6213e05ead22cd6
Gitweb: http://git.kernel.org/tip/b66a2356d7108a15b8b5c9b8e6213e05ead22cd6
Author: anish kumar
AuthorDate: Tue, 12 Mar 2013 14:44:08 -0400
Committer: Ingo Molnar
CommitDate: Thu, 14 Mar 2013 08:24:05 +0100
watchdog: Add comments to
On Tue, Mar 12, 2013 at 11:25 PM, Paul E. McKenney
wrote:
> On Tue, Mar 12, 2013 at 04:02:47PM +0100, Frederic Weisbecker wrote:
>> 2013/3/12 Paul E. McKenney :
>> > On Tue, Mar 12, 2013 at 12:03:23PM +0800, Ming Lei wrote:
>> >> On Tue, Mar 12, 2013 at 11:39 AM, Paul E. McKenney
>> >> wrote:
>>
ACK or NACK this patch please.
On Sat, Mar 9, 2013 at 11:33 AM, anish singh
wrote:
> ping
>
> On Thu, Mar 7, 2013 at 4:41 PM, anish kumar
> wrote:
>> __clocksource_register_scale() currently returns int but it should
>> return void as there are no error paths in tha
ping
On Thu, Mar 7, 2013 at 4:41 PM, anish kumar wrote:
> __clocksource_register_scale() currently returns int but it should
> return void as there are no error paths in that function.
> Making it void would help some amount of code to be removed at various
> places.
>
> clock
will translate to always
if(true) so let's remove those checks as well(patch will be sent
later for that).
Is this return value for some future usecase(?), if yes then my
apologies.
Signed-off-by: anish kumar
---
include/linux/clocksource.h |6 +++---
kernel/time/clocksource.c |
On Tue, Feb 19, 2013 at 2:18 AM, Don Zickus wrote:
> On Sat, Feb 16, 2013 at 05:44:09PM +0530, anish kumar wrote:
>> From: anish kumar
>>
>> This watchdog_disabled flag is bit of cryptic.Howerver it's usefullnes is
>> multifold.
>> Uses are:
>>
On Tue, Feb 26, 2013 at 4:37 PM, Wolfram Sang wrote:
> On Tue, Feb 26, 2013 at 11:02:17AM +0100, Jiri Kosina wrote:
>> On Fri, 22 Feb 2013, 송은봉 wrote:
>>
>> >
>> >
>> >
>> > I've been debugging the abnormal operation of i2c on octeon.
>> > If a process is terminated by signal in the middle of i2c
On Wed, 2013-02-20 at 11:25 +0530, chetan cr123 wrote:
Avoiding top posting.
> Hi Anish,
>
> Thanks for your reply,
>
> I was doing device registration for device by giving same name as
> driver name, This i used to do in platform driver registration,
>
> But i don
On Tue, 2013-02-19 at 12:16 +0530, chetan cr123 wrote:
> HI All,
>
> I am working on Sd Card/Block driver
>
> I am registering it as both
>
> 1. register_blkdev()- BLOCK Regsiter
> 2. mmc_register_driver -- MMC regsiter
>
> and filling the mmc_driver structure.
>
> I am not a
On Sun, 2013-02-17 at 14:37 +, Jonathan Andrews wrote:
> > > The dim pixel code is timing critical (but as I said only a tiny
> > > fraction of the total CPU usage). What I need to do is grab the CPU and
> > > prevent any context switch (IRQ or PREEMPT) for this period.
> > why you want to do t
On Sat, 2013-02-16 at 14:37 +, Jonathan Andrews wrote:
> I hope this is the correct place, I expect to get abused.
>
> I'm trying to do a mostly soft real-time task with a very small hard
> real time element.
>
> I've written some code to drive matrix LED signs using a Raspberry Pi.
>
> Sour
From: anish kumar
This watchdog_disabled flag is bit of cryptic.Howerver it's usefullnes is
multifold.
Uses are:
1. Check if smpboot_register_percpu_thread function passed.
2. Makes sure that user enables and disables the watchdog in sequence
i.e. enable watchdog->disable watchdog
On Sat, 2013-02-16 at 09:42 +0100, Ingo Molnar wrote:
> * Don Zickus wrote:
>
> > > >> > + /*
> > > >> > +* We shouldn't enable watchdog threads if it is
> > > >> > +* disabled.This is done by watchdog_disabled
> > > >> > +* variable check in watchdog_*_all_cpus func
On Thu, 2013-02-14 at 16:33 +, Grant Likely wrote:
> On Thu, 14 Feb 2013 08:57:17 +0530, anish singh
> wrote:
> > On Thu, Feb 14, 2013 at 3:06 AM, Grant Likely
> > wrote:
> > > static int deferred_probe_initcall(void)
> > > {
> > >
On Thu, Feb 14, 2013 at 2:06 PM, anish singh
wrote:
> On Thu, Feb 14, 2013 at 12:56 PM, Dan Carpenter
> wrote:
>> There is a forever loop calling iio_channel_release() because the
>> "chan < " part of the "chan < ARRAY_SIZE()" is missing. This is in
On Thu, Feb 14, 2013 at 12:56 PM, Dan Carpenter
wrote:
> There is a forever loop calling iio_channel_release() because the
> "chan < " part of the "chan < ARRAY_SIZE()" is missing. This is in both
> the error handling on probe and also in the remove function.
>
> The other thing is that it's poss
1 - 100 of 232 matches
Mail list logo
