From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Simon Geis <simon.geis@fau.de>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Colin Ian King <colin.king@canonical.com>,
Adam Zerella <adam.zerella@gmail.com>,
linux-kernel@vger.kernel.org, linux-kernel@i4.cs.fau.de,
Lukas Panzer <lukas.panzer@fau.de>
Subject: Re: [PATCH v3 01/10] PCMCIA/i82092: use dev_<level> instead of printk
Date: Mon, 16 Dec 2019 11:18:34 +0100 [thread overview]
Message-ID: <20191216101834.GA159459@light.dominikbrodowski.net> (raw)
In-Reply-To: <20191213135311.9111-2-simon.geis@fau.de>
On Fri, Dec 13, 2019 at 02:53:04PM +0100, Simon Geis wrote:
> Improve the log output by using the
> device-aware dev_err()/dev_info() functions. While at it, update one
> remaining printk(KERN_ERR ...) call to the preferred pr_err() call
> and delete commented out debugging lines.
>
> Co-developed-by: Lukas Panzer <lukas.panzer@fau.de>
> Signed-off-by: Lukas Panzer <lukas.panzer@fau.de>
> Signed-off-by: Simon Geis <simon.geis@fau.de>
Applied, minus the one hunk which didn't serve any purpose:
> @@ -417,7 +421,9 @@ static int i82092aa_init(struct pcmcia_socket *sock)
>
> static int i82092aa_get_status(struct pcmcia_socket *socket, u_int *value)
> {
> - unsigned int sock = container_of(socket, struct socket_info, socket)->number;
> + struct socket_info *sock_info = container_of(socket, struct socket_info,
> + socket);
> + unsigned int sock = sock_info->number;
> unsigned int status;
>
> enter("i82092aa_get_status");
Thanks,
Dominik
next prev parent reply other threads:[~2019-12-16 11:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 13:53 [PATCH v3 00/10] PCMCIA/i82092: Fix style issues in i82092.c Simon Geis
2019-12-13 13:53 ` [PATCH v3 01/10] PCMCIA/i82092: use dev_<level> instead of printk Simon Geis
2019-12-16 10:18 ` Dominik Brodowski [this message]
2019-12-13 13:53 ` [PATCH v3 02/10] PCMCIA/i82092: add/remove spaces to improve readability Simon Geis
2019-12-16 10:25 ` Dominik Brodowski
2019-12-13 13:53 ` [PATCH v3 03/10] PCMCIA/i82092: remove braces around single statement blocks Simon Geis
2019-12-16 10:29 ` Dominik Brodowski
2019-12-13 13:53 ` [PATCH v3 04/10] PCMCIA/i82092: insert blank line after declarations Simon Geis
2019-12-16 10:30 ` Dominik Brodowski
2019-12-13 13:53 ` [PATCH v3 05/10] PCMCIA/i82092: change code indentation Simon Geis
2019-12-16 10:31 ` Dominik Brodowski
2019-12-13 13:53 ` [PATCH v3 06/10] PCMCIA/i82092: move assignment out of if condition Simon Geis
2019-12-16 10:32 ` Dominik Brodowski
2019-12-13 13:53 ` [PATCH v3 07/10] PCMCIA/i82092: shorten the lines with over 80 characters Simon Geis
2019-12-16 10:35 ` Dominik Brodowski
2019-12-13 13:53 ` [PATCH v3 08/10] PCMCIA/i82092: include <linux/io.h> instead of <asm/io.h> Simon Geis
2019-12-16 10:35 ` Dominik Brodowski
2019-12-13 13:53 ` [PATCH v3 09/10] PCMCIA/i82092: delete enter/leave macro Simon Geis
2019-12-16 10:38 ` Dominik Brodowski
2019-12-13 13:53 ` [PATCH v3 10/10] PCMCIA/i82092: remove #if 0 block Simon Geis
2019-12-16 10:39 ` Dominik Brodowski
2019-12-16 10:58 ` [PATCH v3 00/10] PCMCIA/i82092: Fix style issues in i82092.c Dominik Brodowski
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=20191216101834.GA159459@light.dominikbrodowski.net \
--to=linux@dominikbrodowski.net \
--cc=adam.zerella@gmail.com \
--cc=colin.king@canonical.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@i4.cs.fau.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.panzer@fau.de \
--cc=simon.geis@fau.de \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®