From: Sam Ravnborg <sam@ravnborg.org>
To: Kevin Brace <kevinbrace@gmx.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: How do I gather up new code to be converted as patches?
Date: Fri, 24 Jun 2022 07:16:35 +0200 [thread overview]
Message-ID: <YrVIs89I0aIR3lRh@ravnborg.org> (raw)
In-Reply-To: <trinity-de86d66e-c2f7-4643-8a47-4771e9751cfd-1656026260387@3c-app-mailcom-bs15>
Hi Kevin,
On Fri, Jun 24, 2022 at 01:17:40AM +0200, Kevin Brace wrote:
> Hi Sam,
>
> Okay, I think what you proposed works out for me, although adding 20+ files, one by one, is a pain.
Posting one patch per file works - but sometimes it just makes more
sense to group some files. The process is more or less the same
and it is up to you.
I looked briefly at the link provided in another mail.
It will save you some feedback if you make the files
$checkpatch --strict clean before you submit.
Maybe I confuse this with the older branch I looked at first,
and the current code base is OK.
In drm land most new code is more-or-less checkpatch --strict clean.
There is always the corners cases so do not aim for zero warnings.
Sam
prev parent reply other threads:[~2022-06-24 5:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 17:18 How do I gather up new code to be converted as patches? Kevin Brace
2022-06-22 17:33 ` Jeffrey Hugo
2022-06-23 19:29 ` Kevin Brace
2022-06-23 20:04 ` Thomas Zimmermann
2022-06-22 18:06 ` Sam Ravnborg
2022-06-23 23:17 ` Kevin Brace
2022-06-24 5:16 ` Sam Ravnborg [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=YrVIs89I0aIR3lRh@ravnborg.org \
--to=sam@ravnborg.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kevinbrace@gmx.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.