From: Greg KH <gregkh@linuxfoundation.org>
To: Yusuf Khan <yusisamerican@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jason Wang <jasowang@redhat.com>,
Michael Kelley <mikelley@microsoft.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
javier@javigon.com, Arnd Bergmann <arnd@arndb.de>,
Will Deacon <will@kernel.org>, Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH v7] drivers: ddcci: upstream DDCCI driver
Date: Sat, 12 Mar 2022 07:31:06 +0100 [thread overview]
Message-ID: <Yiw+Kil2BmLPQf7H@kroah.com> (raw)
In-Reply-To: <CAJoG2+9w=GP9=+d=pLuNRoR7USH1V7f=DSPURxnxotYs_CwW+w@mail.gmail.com>
On Fri, Mar 11, 2022 at 09:09:45PM -0800, Yusuf Khan wrote:
> > How can this ever fail?
> If ddcci_verify_device() fails
> > Not needed, just do not have it.
> I'm assuming you mean the locks?
> > This should not be needed in sysfs. What tool wants this?
> Its for the idSerial and modalias part of the userland interface.
> > Why "_void"?
> suppressing "initialization of ‘void (*)(struct device *)’ from
> incompatible pointer type ‘int (*)(struct device *)’"
I have no context at all for this email response, sorry.
Take a look at how email discussions work on the mailing list, with
proper amounts of quoting and the like.
Remember, some of us get at least a thousand emails a day to deal with,
and do not remember what we said in the past, nor what it was about, at
all. By stripping off all context, that ensures we will never remember
it either :(
greg k-h
prev parent reply other threads:[~2022-03-12 6:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 7:44 [PATCH v7] drivers: ddcci: upstream DDCCI driver Yusuf Khan
2022-03-11 8:14 ` Greg KH
2022-03-11 10:45 ` Joe Perches
2022-03-11 11:01 ` Greg KH
2022-03-11 11:16 ` Joe Perches
2022-03-12 5:09 ` Yusuf Khan
2022-03-12 6:31 ` Greg KH [this message]
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=Yiw+Kil2BmLPQf7H@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=jasowang@redhat.com \
--cc=javier@javigon.com \
--cc=linux-kernel@vger.kernel.org \
--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