From: gregkh at linuxfoundation.org (Greg KH)
Subject: [Linux-kernel-mentees] [PATCH v2] replaced both the symbolic permissions S_IXUGO and S_IRUGO to octal permissions 0111 and 0444
Date: Sat, 22 Jun 2019 09:29:04 +0200 [thread overview]
Message-ID: <20190622072904.GA9498@kroah.com> (raw)
In-Reply-To: <20190622071703.9664-1-sushmaunnibhavi425@gmail.com>
On Sat, Jun 22, 2019 at 12:47:03PM +0530, Sushma Unnibhavi wrote:
> Signed-off-by: Sushma Unnibhavi <sushmaunnibhavi425 at gmail.com>
> ---
> Changes in v2:changed both symbolic permissions to octal
> drivers/staging/rtl8723bs/os_dep/rtw_proc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
I'm just going to delete this and wait for a new set on Monday :)
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: gregkh@linuxfoundation.org (Greg KH)
Subject: [Linux-kernel-mentees] [PATCH v2] replaced both the symbolic permissions S_IXUGO and S_IRUGO to octal permissions 0111 and 0444
Date: Sat, 22 Jun 2019 09:29:04 +0200 [thread overview]
Message-ID: <20190622072904.GA9498@kroah.com> (raw)
Message-ID: <20190622072904.jOJIUbjeivTJ40Kor3zw-7aWpTa89uBszaUcYTednSM@z> (raw)
In-Reply-To: <20190622071703.9664-1-sushmaunnibhavi425@gmail.com>
On Sat, Jun 22, 2019 at 12:47:03PM +0530, Sushma Unnibhavi wrote:
> Signed-off-by: Sushma Unnibhavi <sushmaunnibhavi425 at gmail.com>
> ---
> Changes in v2:changed both symbolic permissions to octal
> drivers/staging/rtl8723bs/os_dep/rtw_proc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
I'm just going to delete this and wait for a new set on Monday :)
thanks,
greg k-h
next prev parent reply other threads:[~2019-06-22 7:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-22 7:17 [Linux-kernel-mentees] [PATCH v2] replaced both the symbolic permissions S_IXUGO and S_IRUGO to octal permissions 0111 and 0444 sushmaunnibhavi425
2019-06-22 7:17 ` Sushma Unnibhavi
2019-06-22 7:29 ` gregkh [this message]
2019-06-22 7:29 ` 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=20190622072904.GA9498@kroah.com \
--to=unknown@example.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.