From: emil@limesaudio.com (Emil Lundmark)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: imx: fix integer overflow in AV PLL round rate
Date: Fri, 7 Oct 2016 16:12:25 +0200 [thread overview]
Message-ID: <20161007141224.GA18011@lime> (raw)
In-Reply-To: <1475752331-19525-1-git-send-email-emil@limesaudio.com>
I realize that the two patches in this series does not actually depend on
each other. This is my first contribution to Linux so I wonder if I should
resubmit these as two separate patches instead?
For example, what if the second patch in the series is not needed? Do you
only accept the first patch then? Or what if I need to revise the second
patch? It seems unnecessary to include the first patch in that case.
I also got the threading wrong, but thats another story.
--
Emil Lundmark
next prev parent reply other threads:[~2016-10-07 14:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 11:12 [PATCH 1/2] ARM: imx: fix integer overflow in AV PLL round rate Emil Lundmark
2016-10-06 11:12 ` [PATCH 2/2] ARM: imx: improve precision of AV PLL to 1 Hz Emil Lundmark
2016-10-07 7:48 ` Lothar Waßmann
2016-10-07 13:55 ` Emil Lundmark
2016-10-07 14:12 ` Emil Lundmark [this message]
2016-10-07 15:34 ` [PATCH 1/2] ARM: imx: fix integer overflow in AV PLL round rate Fabio Estevam
2016-10-07 16:02 ` Emil Lundmark
2016-10-07 16:51 ` Fabio Estevam
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=20161007141224.GA18011@lime \
--to=emil@limesaudio.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).