Message ID | 20221010221704.2161221-1-conor@kernel.org (mailing list archive) |
---|---|
Headers | show |
Series | microchip maintainers updates | expand |
On Mon, 10 Oct 2022 15:17:03 PDT (-0700), Conor Dooley wrote: > From: Conor Dooley <conor.dooley@microchip.com> > > Hey Palmer, > > Two maintainers changes that I posted on the lists a while back. > Neither applied at the time b/c the maintainers entry was being updated > in the soc fixes branch and in some for-next branches at the same time > and they conflicted. > > If you could pick the two that'd be great. So you want me to just pick up these patches? That's OK, it's just not a pull request and that's what the subject says. > > Thanks, > Conor. > > Conor Dooley (2): > MAINTAINERS: update polarfire soc clock binding > dt-bindings: riscv: update microchip.yaml's maintainership > > Documentation/devicetree/bindings/riscv/microchip.yaml | 4 ++-- > MAINTAINERS | 3 ++- > 2 files changed, 4 insertions(+), 3 deletions(-)
On Tue, Oct 11, 2022 at 11:20:29AM -0700, Palmer Dabbelt wrote: > On Mon, 10 Oct 2022 15:17:03 PDT (-0700), Conor Dooley wrote: > > From: Conor Dooley <conor.dooley@microchip.com> > > > > Hey Palmer, > > > > Two maintainers changes that I posted on the lists a while back. > > Neither applied at the time b/c the maintainers entry was being updated > > in the soc fixes branch and in some for-next branches at the same time > > and they conflicted. > > > > If you could pick the two that'd be great. > > So you want me to just pick up these patches? Please. > That's OK, it's just not a > pull request and that's what the subject says. Sorry about that. I'd seen people doing it that way for trivial patchsets, eg to arm-soc for dt-bindings, to signify that they were intended to be/ready to be picked directly. I'll stick with "pull" for tags only in the future. Conor.
On Tue, 11 Oct 2022 11:26:12 PDT (-0700), Conor Dooley wrote: > On Tue, Oct 11, 2022 at 11:20:29AM -0700, Palmer Dabbelt wrote: >> On Mon, 10 Oct 2022 15:17:03 PDT (-0700), Conor Dooley wrote: >> > From: Conor Dooley <conor.dooley@microchip.com> >> > >> > Hey Palmer, >> > >> > Two maintainers changes that I posted on the lists a while back. >> > Neither applied at the time b/c the maintainers entry was being updated >> > in the soc fixes branch and in some for-next branches at the same time >> > and they conflicted. >> > >> > If you could pick the two that'd be great. >> >> So you want me to just pick up these patches? > > Please. > >> That's OK, it's just not a >> pull request and that's what the subject says. > > Sorry about that. I'd seen people doing it that way for trivial > patchsets, eg to arm-soc for dt-bindings, to signify that they > were intended to be/ready to be picked directly. I'll stick with > "pull" for tags only in the future. No problem, if that's what folks do then I'm OK with it. I just hadn't seen it before so wasn't sure what was up (doubly so because you send you'd be sending a pull). They're on for-next, hopefully patchwork sends the email too...
From: Conor Dooley <conor.dooley@microchip.com> Hey Palmer, Two maintainers changes that I posted on the lists a while back. Neither applied at the time b/c the maintainers entry was being updated in the soc fixes branch and in some for-next branches at the same time and they conflicted. If you could pick the two that'd be great. Thanks, Conor. Conor Dooley (2): MAINTAINERS: update polarfire soc clock binding dt-bindings: riscv: update microchip.yaml's maintainership Documentation/devicetree/bindings/riscv/microchip.yaml | 4 ++-- MAINTAINERS | 3 ++- 2 files changed, 4 insertions(+), 3 deletions(-)