All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Nigel Christian <nigel.l.christian@gmail.com>
Cc: lee.jones@linaro.org, linux-usb@vger.kernel.org,
	kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] usb: core: ledtrig-usbport: use octal permission
Date: Sun, 01 Nov 2020 06:36:32 +0000	[thread overview]
Message-ID: <20201101063632.GA432136@kroah.com> (raw)
In-Reply-To: <20201031171930.GA21555@fedora-project>

On Sat, Oct 31, 2020 at 01:19:30PM -0400, Nigel Christian wrote:
> Change read/write for owner permission from symbolic to octal
> to enhance readability. This patch reduces checkpatch warnings 
> for this file to nil.
> 
> see: https://lkml.org/lkml/2016/8/2/1945

Please use lore.kernel.org links for mailing list stuff.

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Nigel Christian <nigel.l.christian@gmail.com>
Cc: lee.jones@linaro.org, linux-usb@vger.kernel.org,
	kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] usb: core: ledtrig-usbport: use octal permission
Date: Sun, 1 Nov 2020 07:36:32 +0100	[thread overview]
Message-ID: <20201101063632.GA432136@kroah.com> (raw)
In-Reply-To: <20201031171930.GA21555@fedora-project>

On Sat, Oct 31, 2020 at 01:19:30PM -0400, Nigel Christian wrote:
> Change read/write for owner permission from symbolic to octal
> to enhance readability. This patch reduces checkpatch warnings 
> for this file to nil.
> 
> see: https://lkml.org/lkml/2016/8/2/1945

Please use lore.kernel.org links for mailing list stuff.

thanks,

greg k-h

  reply	other threads:[~2020-11-01  6:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-31 17:19 [PATCH] usb: core: ledtrig-usbport: use octal permission Nigel Christian
2020-10-31 17:19 ` Nigel Christian
2020-11-01  6:36 ` Greg KH [this message]
2020-11-01  6:36   ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201101063632.GA432136@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=nigel.l.christian@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.