lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 12 Apr 2017 10:49:27 +0530 From: Kishon Vijay Abraham I <kishon@...com> To: Lee Jones <lee.jones@...aro.org> CC: <gregkh@...uxfoundation.org>, <linux-kernel@...r.kernel.org> Subject: Re: [PATCH 01/32] mfd: exynos-lpass: Use common soc/exynos-regs-pmu.h header Hi, On Tuesday 11 April 2017 10:04 PM, Lee Jones wrote: > On Tue, 11 Apr 2017, Kishon Vijay Abraham I wrote: > >> Hi, >> >> On Tuesday 11 April 2017 07:44 PM, Lee Jones wrote: >>> On Mon, 10 Apr 2017, Kishon Vijay Abraham I wrote: >>> >>>> From: Krzysztof Kozlowski <krzk@...nel.org> >>>> >>>> The MFD-specific header will go away because it duplicates defines from >>>> exynos-regs-pmu.h. >>>> >>>> Reported-by: kbuild test robot <fengguang.wu@...el.com> >>>> Signed-off-by: Krzysztof Kozlowski <krzk@...nel.org> >>>> Reviewed-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com> >>>> Signed-off-by: Lee Jones <lee.jones@...aro.org> >>> >>> >>> Okay, this is confusing. >>> >>> I'm guessing you're sending this to Greg for inclusion into -stable? >> >> No, it's not for stable. It's for 4.12. > > Then I'm totally confused, since this patch has already been applied, > which is obvious since I already signed it off? With your immutable branch applied to phy tree, it's going to be part of my pull request too. > >>> Isn't there a way to specify this intention? >> >> The pull request (cover letter) specifies this intention. > > Great! But you forgot to send it to me, doh! > > Why are you sending patches with a pull-request? Greg KH sometimes would like to take a look at the patches that are part of the pull request. I've been practicing it for a long time. > >>> Also, patch 1 and 3 appear to be identical. >>> >>> Not even sure how that's possible. > > Still have no idea how you managed to do this! I think first it got applied when I applied patches from local-next to next and then I did a merge of your immutable branch. Thanks Kishon
Powered by blists - more mailing lists