From: Sebastian Reichel <sebastian.reichel@collabora.co.uk>
To: Mark Brown <broonie@kernel.org>
Cc: "Alex A. Mihaylov" <minimumlaw@rambler.ru>,
Evgeniy Polyakov <zbr@ioremap.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regmap: regmap-w1: Fix build troubles
Date: Mon, 10 Jul 2017 15:17:17 +0200 [thread overview]
Message-ID: <20170710131717.grpaai4wjync6g6w@earth> (raw)
In-Reply-To: <20170710121935.aunp4cjnktv57zy4@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1382 bytes --]
Hi,
On Mon, Jul 10, 2017 at 01:19:35PM +0100, Mark Brown wrote:
> On Mon, Jul 10, 2017 at 01:51:38PM +0200, Sebastian Reichel wrote:
> > > Patches like this *really* shouldn't be appearing during the merge
> > > window, they should be being handled well before that with everything
> > > ready in -next when the merge window opens.
>
> > Both patches were in linux-next and both patches have been pulled
> > by Linus. This is broken *now*.
>
> Why are none of the build bots finding problems if this is currently
> broken and why did this not get fixed in -next when it was introduced?
I guess it is because at the moment nothing select REGMAP_W1 in
mainline. I did not (yet) queue the power-supply driver, which
was the initial reason for adding regmap w1 support.
> Like I say I provided a tag for this and didn't get any request to
> pull/apply the update in the other direction so it is extremely
> disappointing to see that the header move went ahead after that without
> the regmap support being included and someone else is having to come
> along and clean up the mess.
FWIW I am just the messenger, who actually pointed out the issue
_before_ it happened in the threads of both patchsets. I expected
this to be properly solved by you and Greg. Since this did not
work out regmap seems now the logical subsystem for the fix.
-- Sebastian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-07-10 13:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 15:38 Alex A. Mihaylov
2017-07-08 14:58 ` Sebastian Reichel
2017-07-10 10:31 ` Mark Brown
2017-07-10 11:51 ` Sebastian Reichel
2017-07-10 12:19 ` Mark Brown
2017-07-10 13:17 ` Sebastian Reichel [this message]
2017-07-10 15:32 ` Mark Brown
[not found] ` <1098881499698175@web19o.yandex.ru>
2017-07-10 14:59 ` Greg Kroah-Hartman
-- strict thread matches above, loose matches on Subject: below --
2017-07-06 13:10 [PATCH] power: power_supply: Add support for MAX1721x standalone fuel gauge Alex A. Mihaylov
2017-07-06 13:10 ` [PATCH] regmap: regmap-w1: Fix build troubles Alex A. Mihaylov
2017-07-07 10:07 ` Mark Brown
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=20170710131717.grpaai4wjync6g6w@earth \
--to=sebastian.reichel@collabora.co.uk \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minimumlaw@rambler.ru \
--cc=zbr@ioremap.net \
/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®