lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <02ea9279-7bdc-43ca-bd7d-898dee14884e@redhat.com>
Date:   Wed, 15 Nov 2023 17:32:20 +0100
From:   Hans de Goede <hdegoede@...hat.com>
To:     Brenton Simpson <appsforartists@...gle.com>
Cc:     Allen Ballway <ballway@...omium.org>,
        Patrick Thompson <ptf@...gle.com>,
        Jared Baldridge <jrb@...unge.us>,
        Emil Velikov <emil.l.velikov@...il.com>,
        Daniel Vetter <daniel.vetter@...ll.ch>,
        linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org
Subject: Re: [PATCH] drm/panel-orientation-quirks: add Lenovo Legion Go

Hi Brenton,

On 11/15/23 16:52, Brenton Simpson wrote:
> Yes, thanks!
> 
> That's the email attached to my public git work, so it should be the
> one here as well.

Ok, I've pushed this to drm-misc-fixes now, thank you for the patch.

> Sorry for the hassle.  Very new to sending PRs over email, and still
> working through the kinks.

Your initial submission was almost there. Just the weird thing
with the + in the From: email-address. What also threw me off
is that the From was: <brentons+appsforartists@...gle.com>

Normally the '+' + the part after it gets thrown away to get
the canonical email address, so that would make your canonical
email: <brentons@...gle.com> where I now know it should be:
<appsforartists@...gle.com> .

So next time you use a + address please do something like:

<appsforartists+brentons@...gle.com>

I also guess you never got any of the replies addressed to
<brentons+appsforartists@...gle.com> since the mail server
presumably has tried to deliver those to <brentons@...gle.com>,
but because your normal email was in the Cc things still
worked out.

Either way for future patches note that using "git send-email"
is the advised way to submit kernel patches.

Regards,

Hans



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ