From: Greg KH <gregkh@linuxfoundation.org>
To: Yusuf Khan <yusisamerican@gmail.com>
Cc: linux-kernel@vger.kernel.org, jasowang@redhat.com,
mikelley@microsoft.com, mst@redhat.com, javier@javigon.com,
arnd@arndb.de, will@kernel.org, axboe@kernel.dk,
Christoph Grenz <christophg+lkml@grenz-bonn.de>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v9 0/3] drivers: ddcci: upstream DDCCI driver
Date: Sun, 27 Mar 2022 09:06:52 +0200 [thread overview]
Message-ID: <YkANDAyCMBBBWEs0@kroah.com> (raw)
In-Reply-To: <20220327045845.144742-1-yusisamerican@gmail.com>
On Sat, Mar 26, 2022 at 09:58:42PM -0700, Yusuf Khan wrote:
> This patch upstreams(adds) the DDCCI driver by Christoph Grenz into
> the kernel. The original gitlab page is loacted at https://gitlab
> .com/ddcci-driver-linux/ddcci-driver-linux/-/tree/master.
>
> DDC/CI is a control protocol for monitor settings supported by most
> monitors since about 2005. A chardev and sysfs interface is provided.
> The seccond patch in this series provides a backlight driver using
> DDC/CI.
>
> Signed-off-by: Yusuf Khan <yusisamerican@gmail.com>
> Signed-off-by: Christoph Grenz <christophg+lkml@grenz-bonn.de>
> ---
> v2: Fix typos.
>
> v3: Add documentation, move files around, replace semaphores with
> mutexes, and replaced <asm-generic/fcntl.h> with <linux/fcntl.h>.
> "imirkin"(which due to his involvement in the dri-devel irc channel
> I cant help but assume to be a DRM developer) said that the DDC/CI
> bus does not intefere with the buses that DRM is involved with.
>
> v4: Move some documentation, fix grammer mistakes, remove usages of
> likely(), and clarify some documentation.
>
> v5: Fix grammer mistakes, remove usages of likely(), and clarify
> some documentation.
>
> v6: Change contact information to reference Christoph Grenz.
>
> v7: Remove all instances of the unlikely() macro.
>
> v8: Modify documentation to provide updated date and kernel
> documentation, fix SPDX lines, use isalpha instead of redefining
> logic, change maximum amount of bytes that can be written to be
> conformant with DDC/CI specification, prevent userspace from holding
> locks with the open file descriptor, remove ddcci_cdev_seek, dont
> refine sysfs_emit() logic, use EXPORT_SYMBOL_GPL instead of
> EXPORT_SYMBOL, remove ddcci_device_remove_void, remove module
> paramaters and version, and split into 2 patches.
>
> v9: Fix IS_ANY_ID matching for compilers and archs where char is
> unsigned char and use the cannonical patch format.
> Reported-by: kernel test robot <lkp@intel.com>
You sent 3 patches with all the same subject line, yet they did
different things. That's not ok at all. Please read the kernel
documentation for how to write proper subject lines.
thanks,
greg k-h
next prev parent reply other threads:[~2022-03-27 7:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-27 4:58 [PATCH v9 0/3] drivers: ddcci: upstream DDCCI driver Yusuf Khan
2022-03-27 4:58 ` [PATCH v9 1/3] " Yusuf Khan
2022-03-27 7:07 ` Greg KH
2022-03-27 4:58 ` [PATCH v9 2/3] " Yusuf Khan
2022-03-27 4:58 ` [PATCH v9 3/3] " Yusuf Khan
2022-03-27 7:06 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-27 4:46 [PATCH v9 0/3] " Yusuf Khan
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=YkANDAyCMBBBWEs0@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=christophg+lkml@grenz-bonn.de \
--cc=jasowang@redhat.com \
--cc=javier@javigon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mikelley@microsoft.com \
--cc=mst@redhat.com \
--cc=will@kernel.org \
--cc=yusisamerican@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox