From: Peter Rosin <peda@axentia.se>
To: Colin Ian King <colin.king@canonical.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
Michal Simek <michal.simek@xilinx.com>,
Johan Hovold <johan@kernel.org>
Cc: "kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][next][V2] i2c: xiic: fix indentation issue
Date: Wed, 29 Jan 2020 08:06:32 +0000 [thread overview]
Message-ID: <f8c236de-4ed6-49dc-e5b7-283ebb859199@axentia.se> (raw)
In-Reply-To: <3b287fb5-e344-c13a-2803-09c2958b9b0d@canonical.com>
On 2020-01-29 00:10, Colin Ian King wrote:
> On 28/01/2020 21:45, Peter Rosin wrote:
>> On 2020-01-27 13:08, Colin Ian King wrote:
>>> On 27/01/2020 12:05, Dan Carpenter wrote:
>>>> On Mon, Jan 27, 2020 at 12:03:02PM +0100, Michal Simek wrote:
>>>>> On 27. 01. 20 11:23, Colin King wrote:
>>>>>> From: Colin Ian King <colin.king@canonical.com>
>>>>>>
>>>>>> There is a statement that is indented one level too deeply, remove
>>>>>> the extraneous tab.
>>>>>>
>>>>>> Signed-off-by: Colin Ian King <colin.king@canonical.com>
>>>>>> ---
>>>>>> V2: fix type in commit message
>>>>>> ---
>>>>>> drivers/i2c/busses/i2c-xiic.c | 2 +-
>>>>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>>>>
>>>>>> diff --git a/drivers/i2c/busses/i2c-xiic.c b/drivers/i2c/busses/i2c-xiic.c
>>>>>> index b17d30c9ab40..90c1c362394d 100644
>>>>>> --- a/drivers/i2c/busses/i2c-xiic.c
>>>>>> +++ b/drivers/i2c/busses/i2c-xiic.c
>>>>>> @@ -261,7 +261,7 @@ static int xiic_clear_rx_fifo(struct xiic_i2c *i2c)
>>>>>> xiic_getreg8(i2c, XIIC_DRR_REG_OFFSET);
>>>>>> if (time_after(jiffies, timeout)) {
>>>>>> dev_err(i2c->dev, "Failed to clear rx fifo\n");
>>>>>> - return -ETIMEDOUT;
>>>>>> + return -ETIMEDOUT;
>>>>>> }
>>>>>> }
>>>>>>
>>>>>>
>>>>>
>>>>> As was suggested by Peter you should also add Fixes: <sha1> ("patch
>>>>> subject")
>>>>>
>>>>
>>>> It's not really a bugfix, it's just a cleanup.
>>>
>>> I'm surprised i wasn't asked for a bug number too.
>>
>> Very funny.
>
> Apologies for being flippant. I didn't mean to offend. My bad #1.
Apology accepted, no hard feelings. Don't worry about it, and sorry on my
part for a possible overreaction!
Cheers,
Peter
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-01-29 8:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 10:23 [PATCH][next][V2] i2c: xiic: fix indentation issue Colin King
2020-01-27 11:03 ` Michal Simek
2020-01-27 11:11 ` Johan Hovold
2020-01-27 12:05 ` Dan Carpenter
2020-01-27 12:08 ` Colin Ian King
2020-01-27 12:11 ` Michal Simek
2020-01-28 21:45 ` Peter Rosin
2020-01-28 23:10 ` Colin Ian King
2020-01-28 23:48 ` Joe Perches
2020-01-29 9:31 ` Peter Rosin
2020-01-29 8:06 ` Peter Rosin [this message]
2020-01-27 11:17 ` Shubhrajyoti Datta
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=f8c236de-4ed6-49dc-e5b7-283ebb859199@axentia.se \
--to=peda@axentia.se \
--cc=colin.king@canonical.com \
--cc=dan.carpenter@oracle.com \
--cc=johan@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.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).