linux-kernel - Re: [PATCH] ASoC: jack - check status of GPIO-based pins on resume

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] [day] [month] [year] [list]

Message-ID: <20170324192855.GC18364@dtor-ws>
Date:   Fri, 24 Mar 2017 12:28:55 -0700
From:   Dmitry Torokhov <dmitry.torokhov@...il.com>
To:     Mark Brown <broonie@...nel.org>
Cc:     Jaroslav Kysela <perex@...ex.cz>,
        Liam Girdwood <lgirdwood@...il.com>,
        Takashi Iwai <tiwai@...e.com>, alsa-devel@...a-project.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: jack - check status of GPIO-based pins on resume

On Fri, Mar 24, 2017 at 07:26:29PM +0000, Mark Brown wrote:
> On Fri, Mar 24, 2017 at 12:22:09PM -0700, Dmitry Torokhov wrote:
> > On Fri, Mar 24, 2017 at 06:51:47PM +0000, Mark Brown wrote:
> 
> > > Please send patches from the mail account corresponding to the signoff,
> > > not doing that makes the patch look like it's missing a signoff (as it's
> > > got the From line so more than one signoff is expected but there's only
> > > one) which slows down review.
> 
> > Resent from @chromium.
> 
> Sorry, that was a note for future submissions - I'd already applied when
> I sent.

Ah, sorry, well, it was a test for my updated script then ;)

-- 
Dmitry