From: Markus Elfring <Markus.Elfring@web.de>
To: Dan Carpenter <dan.carpenter@oracle.com>, linux-kernel@vger.kernel.org
Cc: devel@driverdev.osuosl.org, Michel Lespinasse <walken@google.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Daniel Jordan <daniel.m.jordan@oracle.com>,
Souptick Joarder <jrdr.linux@gmail.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
John Hubbard <jhubbard@nvidia.com>,
Andrew Morton <akpm@linux-foundation.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Vlastimil Babka <vbabka@suse.cz>,
linux-media@vger.kernel.org
Subject: Re: [v2] media: atomisp: Fix error handling path
Date: Wed, 4 Nov 2020 11:30:29 +0100 [thread overview]
Message-ID: <85ff17ad-8aa7-a457-6e23-4f5c1c5152f2@web.de> (raw)
In-Reply-To: <20201104083121.GG18329@kadam>
>>> Fixes: 14a638ab96c5 ("media: atomisp: use pin_user_pages() for memory
>>> allocation")
>>
>> Please delete a line break for this tag.
>
> Markus, the thing is that we all saw the line break and we just thought
> it didn't matter at all...
Do you disagree to the known documentation then?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?id=4ef8451b332662d004df269d4cdeb7d9f31419b5#n123
Regards,
Markus
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2020-11-04 10:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 2:02 [PATCH v2] media: atomisp: Fixed error handling path Souptick Joarder
2020-11-04 7:15 ` [PATCH v2] media: atomisp: Fix " Markus Elfring
2020-11-04 8:31 ` Dan Carpenter
2020-11-04 10:30 ` Markus Elfring [this message]
2020-11-04 11:40 ` [v2] " Dan Carpenter
2020-11-04 20:50 ` Markus Elfring
2020-11-18 19:36 ` [PATCH v2] media: atomisp: Fixed " Souptick Joarder
2020-12-08 19:48 ` Souptick Joarder
2020-12-29 7:48 ` Souptick Joarder
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=85ff17ad-8aa7-a457-6e23-4f5c1c5152f2@web.de \
--to=markus.elfring@web.de \
--cc=akpm@linux-foundation.org \
--cc=dan.carpenter@oracle.com \
--cc=daniel.m.jordan@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=gustavoars@kernel.org \
--cc=jhubbard@nvidia.com \
--cc=jrdr.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=vbabka@suse.cz \
--cc=walken@google.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;
as well as URLs for NNTP newsgroup(s).