Re: [PATCH 2/2] Fixed the format that column is longer than 80 .

[Harry Wei <jiaweiwei.xiyou@gmail.com>]

On Sun, Mar 27, 2011 at 12:25:26AM +0800, Wanlong Gao wrote:
Signed-off-by: Wanlong Gao <wanlong.gao@gmail.com>
Acked-by: Harry Wei <harryxiyou@gmail.com>
> ---
>  mm/memory.c |    9 ++++++---
>  1 files changed, 6 insertions(+), 3 deletions(-)
>  mode change 100644 => 100755 mm/memory.c
> 
> diff --git a/mm/memory.c b/mm/memory.c
> old mode 100644
> new mode 100755
> index 615be51..422cba6
> --- a/mm/memory.c
> +++ b/mm/memory.c
> @@ -2196,7 +2196,8 @@ static inline int pte_unmap_same(struct mm_struct *mm, pmd_t *pmd,
>  	return same;
>  }
>  
> -static inline void cow_user_page(struct page *dst, struct page *src, unsigned long va, struct vm_area_struct *vma)
> +static inline void cow_user_page(struct page *dst, struct page *src,
> +				unsigned long va, struct vm_area_struct *vma)
>  {
>  	/*
>  	 * If the source page was a PFN mapping, we don't have
> @@ -2940,7 +2941,8 @@ out_release:
>   * except we must first make sure that 'address{-|+}PAGE_SIZE'
>   * doesn't hit another vma.
>   */
> -static inline int check_stack_guard_page(struct vm_area_struct *vma, unsigned long address)
> +static inline int check_stack_guard_page(struct vm_area_struct *vma,
> +					unsigned long address)
>  {
>  	address &= PAGE_MASK;
>  	if ((vma->vm_flags & VM_GROWSDOWN) && address == vma->vm_start) {
> @@ -3653,7 +3655,8 @@ int generic_access_phys(struct vm_area_struct *vma, unsigned long addr,
>   * Source/target buffer must be kernel space,
>   * Do not walk the page table directly, use get_user_pages
>   */
> -int access_process_vm(struct task_struct *tsk, unsigned long addr, void *buf, int len, int write)
> +int access_process_vm(struct task_struct *tsk, unsigned long addr,
> +			void *buf, int len, int write)
>  {
>  	struct mm_struct *mm;
>  	struct vm_area_struct *vma;
> -- 
> 1.7.3
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/