From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: mgross@linux.intel.com
Cc: linux-kernel@vger.kernel.org, adam.r.gretzinger@intel.com,
markgross@kernel.org, Seamus Kelly <seamus.kelly@intel.com>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 22/22] xlink-core: factorize xlink_ioctl function by creating sub-functions for each ioctl command
Date: Thu, 26 Nov 2020 21:26:50 +0100 [thread overview]
Message-ID: <X8APikiYF4+C3PjC@kroah.com> (raw)
In-Reply-To: <20201125184349.29686-23-mgross@linux.intel.com>
On Wed, Nov 25, 2020 at 10:43:49AM -0800, mgross@linux.intel.com wrote:
> From: Seamus Kelly <seamus.kelly@intel.com>
>
> Refactor the too large IOCTL function to call helper functions.
>
> Cc: Arnd Bergmann <arnd@arndb.de>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Reviewed-by: Mark Gross <mgross@linux.intel.com>
> Signed-off-by: Seamus Kelly <seamus.kelly@intel.com>
<snip>
What are these random patch sets that don't seem to be showing up on
lore.kernel.org and I don't get the full series, nor any understanding
what is going on?
Are you sending only partial sets out for some reason?
thanks,
greg k-h
next parent reply other threads:[~2020-11-26 20:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201125184349.29686-1-mgross@linux.intel.com>
[not found] ` <20201125184349.29686-23-mgross@linux.intel.com>
2020-11-26 20:26 ` Greg Kroah-Hartman [this message]
2020-11-30 23:06 [PATCH 00/22] Intel Vision Processing Unit base enabling part 1 mgross
2020-11-30 23:07 ` [PATCH 22/22] xlink-core: factorize xlink_ioctl function by creating sub-functions for each ioctl command mgross
-- strict thread matches above, loose matches on Subject: below --
2020-12-01 22:34 [PATCH 00/22] Intel Vision Processing Unit base enabling part 1 mgross
2020-12-01 22:35 ` [PATCH 22/22] xlink-core: factorize xlink_ioctl function by creating sub-functions for each ioctl command mgross
2020-12-07 3:05 ` Joe Perches
2020-12-07 21:59 ` mark gross
2020-12-09 8:30 ` Joe Perches
2020-12-11 11:36 ` Kelly, Seamus
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=X8APikiYF4+C3PjC@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=adam.r.gretzinger@intel.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=mgross@linux.intel.com \
--cc=seamus.kelly@intel.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.