From: "Williams, Dan J" <dan.j.williams@intel.com>
To: Greg KH <gregkh@suse.de>
Cc: Greg KH <greg@kroah.com>, Nhan H Mai <nhan.h.mai@intel.com>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
alan@linux.intel.com
Subject: Re: [PATCH] serial/8250_pci: add a quirk for the kt serial controller
Date: Tue, 25 Oct 2011 15:52:20 -0700 [thread overview]
Message-ID: <CABE8wwugFuNUstAFxKGLyZthAk+Cb9MN3kQFDr-vN08pdsMoRA@mail.gmail.com> (raw)
In-Reply-To: <20111025205106.GD7234@suse.de>
On Tue, Oct 25, 2011 at 1:51 PM, Greg KH <gregkh@suse.de> wrote:
> On Tue, Oct 25, 2011 at 01:16:34PM -0700, Dan Williams wrote:
>> From: Dan Williams <dan.j.williams@intel.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@intel.com>
>> Signed-off-by: Dan Williams <dan.j.williams@intel.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-serial" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-10-25 22:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-23 22:27 [PATCH] serial/8250_pci: add a quirk for the kt serial controller Dan Williams
2011-10-25 2:28 ` Greg KH
2011-10-25 20:16 ` Dan Williams
2011-10-25 20:51 ` Greg KH
2011-10-25 22:52 ` Williams, Dan J [this message]
2011-11-03 16:34 ` Williams, Dan J
2011-11-15 19:18 ` Greg KH
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=CABE8wwugFuNUstAFxKGLyZthAk+Cb9MN3kQFDr-vN08pdsMoRA@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=alan@linux.intel.com \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=nhan.h.mai@intel.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).