From: Ruslan Babayev <ruslan@babayev.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Ruslan Babayev <ruslan@babayev.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
xe-linux-external@cisco.com, linux-i2c@vger.kernel.org,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 1/2] i2c: acpi: export i2c_acpi_find_adapter_by_handle
Date: Mon, 27 May 2019 19:03:44 -0700 [thread overview]
Message-ID: <874l5f9vy7.fsf@babayev.com> (raw)
In-Reply-To: <20190527184743.GA8808@kunai>
Wolfram Sang writes:
> On Fri, May 24, 2019 at 05:53:01PM -0700, Ruslan Babayev wrote:
>> This allows drivers to lookup i2c adapters on ACPI based systems similar to
>> of_get_i2c_adapter_by_node() with DT based systems.
>>
>> Signed-off-by: Ruslan Babayev <ruslan@babayev.com>
>> Cc: xe-linux-external@cisco.com
>
> Please have a look how your patches look in my inbox:
>
> May 05 Ruslan Babayev ( 129) [PATCH] net: phy: sfp: enable i2c-bus detection on ACPI based systems
> May 05 Ruslan Babayev ( 65) ├─>[PATCH 1/2] i2c: acpi: export i2c_acpi_find_adapter_by_handle
> May 24 Ruslan Babayev ( 65) └─>[PATCH net-next v2 1/2] i2c: acpi: export i2c_acpi_find_adapter_by_handle
> May 05 Ruslan Babayev ( 65) [PATCH net-next 1/2] i2c: acpi: export i2c_acpi_find_adapter_by_handle
> May 06 Ruslan Babayev ( 3) ├─>[PATCH RFC v2 net-next] Enable SFP support on ACPI
> May 06 Ruslan Babayev ( 65) ├─>[PATCH RFC v2 net-next 1/2] i2c: acpi: export i2c_acpi_find_adapter_by_handle
> May 06 Ruslan Babayev ( 120) └─>[PATCH RFC v2 net-next 2/2] net: phy: sfp: enable i2c-bus detection on ACPI based systems
> May 07 Ruslan Babayev ( 154) └─&─>
> May 07 Ruslan Babayev ( 10) └─>
> May 22 Ruslan Babayev ( 29) └─>
> May 05 Ruslan Babayev ( 93) [PATCH net-next 2/2] net: phy: sfp: enable i2c-bus detection on ACPI based systems
> May 06 Ruslan Babayev ( 25) ├─&─>
> May 06 Ruslan Babayev ( 99) └─&─>
>
> This is highly confusing, and super hard to find out which patches belong
> together. v2 2/2 seems even missing. Please resend this as a new series without
> any in-reply-to, and a fresh cover-letter, so I know which one to apply to my
> tree.
>
> Thanks,
>
> Wolfram
Will do, sorry about that.
prev parent reply other threads:[~2019-05-28 2:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-05 19:34 [PATCH] net: phy: sfp: enable i2c-bus detection on ACPI based systems Ruslan Babayev
2019-05-05 19:34 ` Ruslan Babayev
2019-05-05 19:51 ` Heiner Kallweit
2019-05-05 19:51 ` Heiner Kallweit
2019-05-05 20:51 ` [PATCH 1/2] i2c: acpi: export i2c_acpi_find_adapter_by_handle Ruslan Babayev
2019-05-05 20:51 ` Ruslan Babayev
2019-05-25 0:53 ` [PATCH net-next v2 " Ruslan Babayev
2019-05-27 8:39 ` Mika Westerberg
2019-05-28 2:26 ` Ruslan Babayev
2019-05-27 18:47 ` Wolfram Sang
2019-05-28 2:03 ` Ruslan Babayev [this message]
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=874l5f9vy7.fsf@babayev.com \
--to=ruslan@babayev.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=wsa@the-dreams.de \
--cc=xe-linux-external@cisco.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