On Sat, Jul 12, 2014 at 09:59:09PM -0700, Anand Moon wrote:
> Hi All,
>
> I would like to know a procedure to extract linux-headers from linux src tree.
make headers_install
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.ke
Hi All,
I would like to know a procedure to extract linux-headers from linux src tree.
-Anand Moon
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
On Sat, 2014-07-12 at 12:28 -0700, Greg KH wrote:
> On Sat, Jul 12, 2014 at 11:29:37AM -0700, Joe Perches wrote:
> > On Sat, 2014-07-12 at 10:55 -0700, Greg KH wrote:
> > > Yes, the warnings are all due to line-length, but Joe, you shouldn't add
> > > a patch that causes more checkpatch warnings th
On Sat, 2014-07-12 at 10:55 -0700, Greg KH wrote:
> Yes, the warnings are all due to line-length, but Joe, you shouldn't add
> a patch that causes more checkpatch warnings than before :)
Yeah, that was intentional though.
This script does a series of relatively discrete changes.
Lindent would mo
On Fri, 2014-07-11 at 18:53 -0700, Greg KH wrote:
> On Fri, Jul 11, 2014 at 06:21:27PM -0700, Joe Perches wrote:
> > A simple script to run checkpatch --fix for various types of
> > of cleanups.
[]
> Anyway, try running this script on
> drivers/staging/lustre/lnet/lnet/acceptor.c to see how this bu
On Sat, 2014-07-12 at 01:18 -0700, Greg KH wrote:
> On Fri, Jul 11, 2014 at 06:21:27PM -0700, Joe Perches wrote:
> > A simple script to run checkpatch --fix for various types of
> > of cleanups.
[]
> I did the following:
>
> $ scripts/reformat_with_checkpatch.sh drivers/base/bus.c
>
> Ignore the
There's a useless "+" use that needs to be removed as perl 5.20
emits a "Useless use of greediness modifier '+'" message each
time it's hit.
Reported-by: Greg KH
Signed-off-by: Joe Perches
---
On Fri, 2014-07-11 at 19:05 -0700, Greg KH wrote:
> Ok, with linux-next I get the same thing:
Thanks G
On Fri, 2014-07-11 at 18:39 -0700, Greg KH wrote:
> On Fri, Jul 11, 2014 at 06:21:27PM -0700, Joe Perches wrote:
> > A simple script to run checkpatch --fix for various types of
> > of cleanups.
]
> drivers/staging/lustre/include/linux/lnet/api.h has no obvious style problems
> and is ready for su
On Fri, 2014-07-11 at 18:43 -0700, Greg KH wrote:
> On Fri, Jul 11, 2014 at 06:21:27PM -0700, Joe Perches wrote:
> > A simple script to run checkpatch --fix for various types of
> > of cleanups.
[]
> If I pick drivers/staging/lustre/include/linux/lnet/types.h, then I get:
>
> staging: lnet:
On Fri, 2014-07-11 at 18:34 -0700, Greg KH wrote:
> On Fri, Jul 11, 2014 at 06:21:27PM -0700, Joe Perches wrote:
> > A simple script to run checkpatch --fix for various types of
> > of cleanups.
> >
> > This script is useful primarily for staging.
> >
> > This reformats code to a more CodingStyle
A simple script to run checkpatch --fix for various types of
of cleanups.
This script is useful primarily for staging.
This reformats code to a more CodingStyle conforming style,
compiles it, verifies that the object code hasn't changed,
and git commits it too.
You must have the necessary develo
On Thu, 10 Jul 2014, Pranith Kumar wrote:
> > Correct.
>
> I understand one of the advantage of using these per cpu variables is
> avoiding disabling interrupts. But what happens when this cpu is
> preempted? The new processor will be working on the other cpu
> variables, but without barriers will
On Thu, 10 Jul 2014, Pranith Kumar wrote:
> Hello,
>
> Let us say we have a per-cpu data structure as follows:
>
> struct data {
> atomic_t val;
> };
>
> Since this is a per-cpu data structure, do I need to have 'val' as
> atomic? Or can I just use a normal 'int' for val?
Per cpu data str
On Thu, 10 Jul 2014, Pranith Kumar wrote:
> > Per cpu data structures are for the use of one cpu exclusively. If you use
> > the variable as intended then there is no atomic_t required. If you want
> > to update the percpu variable from other processors then atomic_t is
> > required. But then this
Hello,
Let us say we have a per-cpu data structure as follows:
struct data {
atomic_t val;
};
Since this is a per-cpu data structure, do I need to have 'val' as
atomic? Or can I just use a normal 'int' for val?
Also are the following the same? If yes, which is preferable?
DEFINE_PER_CP
Hi,
i find that even when /proc/sys/net/ipv4/ip_no_pmtu_disc is 0 (default
value), that
is path mtu is enabled, IP layer fragments the packets if it exceeds MTU
For example MTU is 1500, i do ping -s 15000 , IP layer nicely fragments
the packets, how is that possible?
Does that mean PATH MTU is e
On Sat, Jul 12, 2014 at 11:29:37AM -0700, Joe Perches wrote:
> On Sat, 2014-07-12 at 10:55 -0700, Greg KH wrote:
> > Yes, the warnings are all due to line-length, but Joe, you shouldn't add
> > a patch that causes more checkpatch warnings than before :)
>
> Yeah, that was intentional though.
>
>
On Sat, Jul 12, 2014 at 12:30:43PM +0300, Dan Carpenter wrote:
> On Fri, Jul 11, 2014 at 06:40:16PM -0700, Joe Perches wrote:
> > On Fri, 2014-07-11 at 18:34 -0700, Greg KH wrote:
> > > On Fri, Jul 11, 2014 at 06:21:27PM -0700, Joe Perches wrote:
> > > > A simple script to run checkpatch --fix for
On Fri, Jul 11, 2014 at 06:40:16PM -0700, Joe Perches wrote:
> On Fri, 2014-07-11 at 18:34 -0700, Greg KH wrote:
> > On Fri, Jul 11, 2014 at 06:21:27PM -0700, Joe Perches wrote:
> > > A simple script to run checkpatch --fix for various types of
> > > of cleanups.
> > >
> > > This script is useful
On Fri, Jul 11, 2014 at 06:21:27PM -0700, Joe Perches wrote:
> A simple script to run checkpatch --fix for various types of
> of cleanups.
>
> This script is useful primarily for staging.
>
> This reformats code to a more CodingStyle conforming style,
> compiles it, verifies that the object code
On Fri, Jul 11, 2014 at 06:57:24PM -0700, Joe Perches wrote:
> On Fri, 2014-07-11 at 18:53 -0700, Greg KH wrote:
> > On Fri, Jul 11, 2014 at 06:21:27PM -0700, Joe Perches wrote:
> > > A simple script to run checkpatch --fix for various types of
> > > of cleanups.
> []
> > Anyway, try running this s
Got mine a few days back. Patience
On Sat 12 Jul 2014 12:23:12 AM IST, Jake Mitchell wrote:
> On Fri, 11 Jul 2014, Narendra Joshi wrote:
>
>> I am waiting for the results of my task03 submission for almost a week now.
>> Has anyone been getting replies meanwhile?
>> --
>> Narendra Joshi
>>
>
> Not
22 matches
Mail list logo