it uses 'u32' and 'u64'.
Signed-off-by: Roman Storozhenko <romeusmeis...@gmail.com>
---
In the third version of that patch Dan Carpenter pointed out that the patch
body should be self-explanatory:
"
> There are two reasons for that:
What I'm asking is there are two reasons fo
On Mon, Dec 04, 2017 at 10:58:23PM +0300, Dan Carpenter wrote:
> On Wed, Nov 29, 2017 at 07:46:21PM +0300, Roman Storozhenko wrote:
> > There are two reasons for that:
>
> What I'm asking is there are two reasons for what? Where is the first
> part of that paragraph?
On Thu, Nov 30, 2017 at 09:08:46AM +0300, Dan Carpenter wrote:
> On Wed, Nov 29, 2017 at 07:46:21PM +0300, Roman Storozhenko wrote:
> > There are two reasons for that:
>
> In my email client the subject line and body are not next to each other.
> It looks like this:
>
&
There are two reasons for that:
1) As Linus Torvalds said we should use kernel types:
http://lkml.iu.edu/hypermail//linux/kernel/1506.0/00160.html
2) There are only few places in the lustre codebase that use such types.
In the most cases it uses 'u32' and 'u64'.
Signed-off-by: Roman Storozhenko
There are two reasons for that:
1) As Linus Torvalds said we should use kernel types:
http://lkml.iu.edu/hypermail//linux/kernel/1506.0/00160.html
2) There are only few places in the lustre codebase that use such types.
In the most cases it uses 'u32' and 'u64'.
Signed-off-by: Roman Storozhenko
On Thu, Nov 9, 2017 at 1:06 PM, Dilger, Andreas
<andreas.dil...@intel.com> wrote:
> On Nov 3, 2017, at 06:36, Roman Storozhenko <romeusmeis...@gmail.com> wrote:
>>
>> On Fri, Nov 03, 2017 at 12:46:18PM +0100, Greg Kroah-Hartman wrote:
>>> On Sun, Oct 29, 2017 at
On Fri, Nov 03, 2017 at 12:46:18PM +0100, Greg Kroah-Hartman wrote:
> On Sun, Oct 29, 2017 at 08:58:39PM +0300, Roman Storozhenko wrote:
> > There are two reasons for that:
> > 1) As Linus Torvalds said we should use kernel types:
> > http://lkml.iu.edu/hypermail//linux/ker
There are two reasons for that:
1) As Linus Torvalds said we should use kernel types:
http://lkml.iu.edu/hypermail//linux/kernel/1506.0/00160.html
2) There are only few places in the lustre codebase that use such types.
In the most cases it uses '__u32' and '__u64'.
Signed-off-by: Roman
On Fri, Jun 09, 2017 at 04:30:02PM +0300, Roman Storozhenko wrote:
> Use 'const' in declarations of various 'file_operations' structures.
>
> Signed-off-by: Roman Storozhenko <romeusmeis...@gmail.com>
> ---
> drivers/staging/lustre/lustre/llite/file.c | 6 +++---
> 1 fi
improve the system]
>
> url:
> https://github.com/0day-ci/linux/commits/Roman-Storozhenko/staging-lustre-llite-Make-structure-describing-various-file-operations-const/20170610-121428
> config: sparc64-allmodconfig (attached as .config)
> compiler: sparc64-linux-gnu-gcc (Debian 6.
Fixes a style problems. Replaces non-standard 'Lx' specifier with a
standard 'llx'.
Signed-off-by: Roman Storozhenko <romeusmeis...@gmail.com>
---
drivers/staging/lustre/lustre/fid/fid_request.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/lustre/lust
Use 'const' in declarations of various 'file_operations' structures.
Signed-off-by: Roman Storozhenko <romeusmeis...@gmail.com>
---
drivers/staging/lustre/lustre/llite/file.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/lustre/lustre/llite/fil
12 matches
Mail list logo
