From: Dan Carpenter <dan.carpenter@oracle.com>
To: Mathieu Malaterre <malat@debian.org>
Cc: qiang.zhao@nxp.com, kernel-janitors@vger.kernel.org,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
LKML <linux-kernel@vger.kernel.org>,
leoyang.li@nxp.com
Subject: Re: [PATCH] fsl/qe: ucc: copy and paste bug in ucc_get_tdm_sync_shift()
Date: Wed, 29 Aug 2018 12:39:48 +0300 [thread overview]
Message-ID: <20180829093948.c7nbl27ju4uszrum@mwanda> (raw)
In-Reply-To: <CA+7wUszWKm+qZQ7CQu3Kn7-aYeM-hSet03_PEh8EswNn141nyw@mail.gmail.com>
On Mon, Jun 04, 2018 at 02:06:45PM +0200, Mathieu Malaterre wrote:
> Where did the original go ?
>
> https://patchwork.ozlabs.org/patch/868158/
>
>
Btw, we still haven't pushed a patch for this bug.
regards,
dan carpenter
next prev parent reply other threads:[~2018-08-29 9:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 11:58 [PATCH] fsl/qe: ucc: copy and paste bug in ucc_get_tdm_sync_shift() Dan Carpenter
2018-06-04 12:06 ` Mathieu Malaterre
2018-08-29 9:39 ` Dan Carpenter [this message]
2018-08-29 22:41 ` Li Yang
2018-06-04 13:25 ` Julia Lawall
2018-06-04 13:40 ` Dan Carpenter
2018-06-04 13:46 ` Julia Lawall
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=20180829093948.c7nbl27ju4uszrum@mwanda \
--to=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=malat@debian.org \
--cc=qiang.zhao@nxp.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