From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Keyur Patel <iamkeyur96@gmail.com>
Cc: Markus Elfring <Markus.Elfring@web.de>,
devel@driverdev.osuosl.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org,
Suresh Udipi <sudipi@jp.adit-jv.com>,
Colin Ian King <colin.king@canonical.com>,
Christian Gromm <christian.gromm@microchip.com>
Subject: Re: [v4] staging: most: remove redundant print statement when kfifo_alloc fails
Date: Mon, 15 Jul 2019 09:32:57 +0200 [thread overview]
Message-ID: <20190715073257.GB2100@kroah.com> (raw)
In-Reply-To: <20190714154737.GB32464@keyur-pc>
On Sun, Jul 14, 2019 at 11:47:37AM -0400, Keyur Patel wrote:
> I didn't get you. I stiil need to update changelog and send more
> version or not. If you say so, I can send one more.
Please note that the person/bot you are responding to is on in my email
blacklist, and many others, so I wouldn't worry too much about the
responses.
I'll review this patch once 5.3-rc1 is out as I can't do anything with
it during the merge window.
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: kernel-janitors@vger.kernel.org
Subject: Re: [v4] staging: most: remove redundant print statement when kfifo_alloc fails
Date: Mon, 15 Jul 2019 07:32:57 +0000 [thread overview]
Message-ID: <20190715073257.GB2100@kroah.com> (raw)
In-Reply-To: <20190714154737.GB32464@keyur-pc>
On Sun, Jul 14, 2019 at 11:47:37AM -0400, Keyur Patel wrote:
> I didn't get you. I stiil need to update changelog and send more
> version or not. If you say so, I can send one more.
Please note that the person/bot you are responding to is on in my email
blacklist, and many others, so I wouldn't worry too much about the
responses.
I'll review this patch once 5.3-rc1 is out as I can't do anything with
it during the merge window.
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: gregkh@linuxfoundation.org (Greg Kroah-Hartman)
Subject: [v4] staging: most: remove redundant print statement when kfifo_alloc fails
Date: Mon, 15 Jul 2019 09:32:57 +0200 [thread overview]
Message-ID: <20190715073257.GB2100@kroah.com> (raw)
In-Reply-To: <20190714154737.GB32464@keyur-pc>
On Sun, Jul 14, 2019@11:47:37AM -0400, Keyur Patel wrote:
> I didn't get you. I stiil need to update changelog and send more
> version or not. If you say so, I can send one more.
Please note that the person/bot you are responding to is on in my email
blacklist, and many others, so I wouldn't worry too much about the
responses.
I'll review this patch once 5.3-rc1 is out as I can't do anything with
it during the merge window.
thanks,
greg k-h
next prev parent reply other threads:[~2019-07-15 7:33 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 11:08 [PATCH 2/2] staging: most: remove redundant print statement when kfifo_alloc fails Keyur Patel
2019-07-11 11:08 ` Keyur Patel
2019-07-11 17:39 ` [PATCH v2] staging: most: remove redundant print statement when Keyur Patel
2019-07-11 17:39 ` Keyur Patel
2019-07-11 17:50 ` [PATCH v3] staging: most: remove redundant print statement when kfifo_alloc fails Keyur Patel
2019-07-11 17:50 ` Keyur Patel
2019-07-14 14:42 ` [v3] " Markus Elfring
2019-07-14 14:42 ` Markus Elfring
2019-07-14 14:42 ` Markus Elfring
2019-07-14 15:05 ` [PATCH v4] " Keyur Patel
2019-07-14 15:05 ` Keyur Patel
2019-07-14 15:23 ` [v4] " Markus Elfring
2019-07-14 15:23 ` Markus Elfring
2019-07-14 15:23 ` Markus Elfring
2019-07-14 15:45 ` Keyur Patel
2019-07-14 15:45 ` Keyur Patel
2019-07-14 15:45 ` Keyur Patel
2019-07-14 15:47 ` Keyur Patel
2019-07-14 15:47 ` Keyur Patel
2019-07-14 15:47 ` Keyur Patel
2019-07-14 16:20 ` Markus Elfring
2019-07-14 16:20 ` Markus Elfring
2019-07-14 16:20 ` Markus Elfring
2019-07-15 7:32 ` Greg Kroah-Hartman [this message]
2019-07-15 7:32 ` Greg Kroah-Hartman
2019-07-15 7:32 ` Greg Kroah-Hartman
2019-07-14 16:41 ` [PATCH v4] staging: most: Delete an error message for a failed memory allocation Keyur Patel
2019-07-14 16:41 ` Keyur Patel
2019-07-14 16:55 ` [v4] " Markus Elfring
2019-07-14 16:55 ` Markus Elfring
2019-07-14 16:55 ` Markus Elfring
2019-07-14 17:04 ` Keyur Patel
2019-07-14 17:04 ` Keyur Patel
2019-07-14 17:04 ` Keyur Patel
2019-07-14 17:12 ` Markus Elfring
2019-07-14 17:12 ` Markus Elfring
2019-07-14 17:12 ` Markus Elfring
2019-07-14 17:27 ` [PATCH v5] " Keyur Patel
2019-07-14 17:27 ` Keyur Patel
2019-07-14 17:38 ` [v5] " Markus Elfring
2019-07-14 17:38 ` Markus Elfring
2019-07-14 17:38 ` Markus Elfring
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=20190715073257.GB2100@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Markus.Elfring@web.de \
--cc=christian.gromm@microchip.com \
--cc=colin.king@canonical.com \
--cc=devel@driverdev.osuosl.org \
--cc=iamkeyur96@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudipi@jp.adit-jv.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.