[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABE8wwugFuNUstAFxKGLyZthAk+Cb9MN3kQFDr-vN08pdsMoRA@mail.gmail.com>
Date: Tue, 25 Oct 2011 15:52:20 -0700
From: "Williams, Dan J" <dan.j.williams@...el.com>
To: Greg KH <gregkh@...e.de>
Cc: Greg KH <greg@...ah.com>, Nhan H Mai <nhan.h.mai@...el.com>,
linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org,
alan@...ux.intel.com
Subject: Re: [PATCH] serial/8250_pci: add a quirk for the kt serial controller
On Tue, Oct 25, 2011 at 1:51 PM, Greg KH <gregkh@...e.de> wrote:
> On Tue, Oct 25, 2011 at 01:16:34PM -0700, Dan Williams wrote:
>> From: Dan Williams <dan.j.williams@...el.com>
>> Date: Sun, 23 Oct 2011 15:06:24 -0700
>> Subject: [PATCH v2] serial/8250_pci: add a quirk for the kt serial controller
>>
>> Workaround dropped notifications in the iir register. Prevent reads
>> coincident with new interrupt notifications by reading the iir at most
>> once per interrupt.
>>
>> Reported-by: Nhan H Mai <nhan.h.mai@...el.com>
>> Signed-off-by: Dan Williams <dan.j.williams@...el.com>
>
> Much better.
>
> But.
>
> Do you really think I can apply a patch that looks like this above? I
> have to edit the text of the email before I apply it.
I don't doubt you get busted patches all the time, this isn't one.
Double checked before and now triple checked that git am takes the
last occurrence of the From: Date: and Subject: headers and that my
mailer is not corrupting the patch.
I have no problem resending to fit into your workflow, but I expect
"git am" will do the right thing with this mail.
--
Dan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists