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 13:51:38 +0200 [thread overview]
Message-ID: <20170710115138.c7dwbhuk7lxbrigg@earth> (raw)
In-Reply-To: <20170710103141.teuhsi7o3b4grxjw@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1396 bytes --]
Hi,
On Mon, Jul 10, 2017 at 11:31:41AM +0100, Mark Brown wrote:
> On Sat, Jul 08, 2017 at 04:58:08PM +0200, Sebastian Reichel wrote:
> > On Fri, Jul 07, 2017 at 06:38:22PM +0300, Alex A. Mihaylov wrote:
> > > Fixes: cc5d0db390b0 ("regmap: Add 1-Wire bus support")
> > > Commit de0d6dbdbdb2 ("w1: Add subsystem kernel public interface")
> > > Fix place off w1.h header file
>
> > > Cosmetic: Fix company name (local to international)
>
> > > Signed-off-by: Alex A. Mihaylov <minimumlaw@rambler.ru>
>
> > This should go into 4.13, but you actually did not include the
> > maintainer of regmap (which I just added, but you may have to
> > resend the patch, so that it lands in his inbox). Anyways the
> > change is:
>
> No, he sent it to me originally and I redirected him to whoever has
> moved the header file - the regmap code is in Linus' tree already, if
> the header file is going to be moved this needs to include the regmap
> support and this patch. I did at the time provide a signed tag for the
> regmap 1wire support for precisely this purpose :(
>
> 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*.
-- Sebastian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-07-10 11:51 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 [this message]
2017-07-10 12:19 ` Mark Brown
2017-07-10 13:17 ` Sebastian Reichel
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=20170710115138.c7dwbhuk7lxbrigg@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®