[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGRGNgWDJqV=XD+6q26Ma=m1sEi1kvLWsjq6=RjRVSFTxow0Qg@mail.gmail.com>
Date: Mon, 8 Dec 2014 10:44:40 +1100
From: Julian Calaby <julian.calaby@...il.com>
To: Julia Lawall <Julia.Lawall@...6.fr>
Cc: linux-wireless <linux-wireless@...r.kernel.org>,
kernel-janitors@...r.kernel.org, linux@...musvillemoes.dk,
Joe Perches <joe@...ches.com>,
"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
linux-scsi <linux-scsi@...r.kernel.org>,
dri-devel@...ts.freedesktop.org, intel-gfx@...ts.freedesktop.org,
linux-mtd@...ts.infradead.org, linux-samsung-soc@...r.kernel.org,
"Mailing List, Arm" <linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-pci@...r.kernel.org, netdev <netdev@...r.kernel.org>,
linux-usb@...r.kernel.org
Subject: Re: [PATCH 0/20] fix misspelling of current function in string
Hi Julia,
On Mon, Dec 8, 2014 at 6:20 AM, Julia Lawall <Julia.Lawall@...6.fr> wrote:
> These patches replace what appears to be a reference to the name of the
> current function but is misspelled in some way by either the name of the
> function itself, or by %s and then __func__ in an argument list.
Would there be any value in doing this for _all_ cases where the
function name is written in a format string?
Thanks,
--
Julian Calaby
Email: julian.calaby@...il.com
Profile: http://www.google.com/profiles/julian.calaby/
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists